Priority of Beam Failure Recovery Request and Uplink Channels

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A wireless device may distribute power for various transmission types based on a priority, which may be received from a base station.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/543,826, titled “Priority of BFR Request and Uplink Channels,” whichwas filed on Aug. 10, 2017, and which is hereby incorporated byreference in its entirety.

BACKGROUND

In wireless communications, beam failure recovery may be used forrecovering a beam pair link between a base station and a wirelessdevice. If a beam failure is detected, difficulties may arise inperforming beam failure recovery in a timely and efficient manner.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for communicationsassociated with beam failure recovery. A base station may transmit, to awireless device, one or more messages comprising configurationparameters for beam failure recovery. The configuration parameters maycomprise an indication of beam failure recovery priority information forthe wireless device. The priority information may be predefined orpreconfigured. The wireless device may detect a beam failure. Thewireless device may adjust transmission power based on the priorityinformation so as not to exceed a total transmission power thresholdwhen performing beam failure recovery.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows example sets of orthogonal frequency division multiplexing(OFDM) subcarriers.

FIG. 2 shows example transmission time and reception time for twocarriers in a carrier group.

FIG. 3 shows example OFDM radio resources.

FIG. 4 shows hardware elements of a base station and a wireless device.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D show examples for uplink anddownlink signal transmission.

FIG. 6 shows an example protocol structure with multi-connectivity.

FIG. 7 shows an example protocol structure with carrier aggregation (CA)and dual connectivity (DC).

FIG. 8 shows example timing advance group (TAG) configurations.

FIG. 9 shows example message flow in a random access process in asecondary TAG.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork and base stations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F showexamples for architectures of tight interworking between a 5G RAN and along term evolution (LTE) radio access network (RAN).

FIG. 12A, FIG. 12B, and FIG. 12C show examples for radio protocolstructures of tight interworking bearers.

FIG. 13A and FIG. 13B show examples for gNodeB (gNB) deployment.

FIG. 14 shows functional split option examples of a centralized gNBdeployment.

FIG. 15 shows an example of a synchronization signal burst set.

FIG. 16 shows an example of a random access procedure.

FIG. 17 shows an example of transmitting channel state informationreference signals periodically for a beam.

FIG. 18 shows an example of a channel state information reference signalmapping.

FIG. 19 shows an example of a beam failure event involving a singletransmission and receiving point.

FIG. 20 shows an example of a beam failure event involving multipletransmission and receiving points.

FIG. 21 shows an example of a BFR-PRACH transmission in conjunction witha regulated transmission.

FIG. 22 shows an example of a BFR request transmission in a multiple-TRPsystem.

FIG. 23 shows an example of processes for a wireless device for beamfailure recovery requests.

FIG. 24 shows an example of processes for a base station for beamfailure recovery requests.

FIG. 25 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings, which form a part hereof, show examples ofthe disclosure. It is to be understood that the examples shown in thedrawings and/or discussed herein are non-exclusive and that there areother examples of how the disclosure may be practiced.

Examples may enable operation of carrier aggregation and may be employedin the technical field of multicarrier communication systems. Examplesmay relate to beam failure recovery in a multicarrier communicationsystem.

The following acronyms are used throughout the present disclosure,provided below for convenience although other acronyms may be introducedin the detailed description:

3GPP 3rd Generation Partnership Project

5G 5th generation wireless systems

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ASIC application-specific integrated circuit

BFR beam failure recovery

BPSK binary phase shift keying

CA carrier aggregation

CC component carrier

CDMA code division multiple access

CP cyclic prefix

CPLD complex programmable logic devices

CSI channel state information

CSS common search space

CU central unit

DC dual connectivity

DCI downlink control information

DFTS-OFDM discrete fourier transform spreading OFDM

DL downlink

DU distributed unit

eLTE enhanced LTE

eMBB enhanced mobile broadband

eNB evolved Node B

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FDD frequency division multiplexing

FPGA field programmable gate arrays

Fs-C Fs-control plane

Fs-U Fs-user plane

gNB next generation node B

HARQ hybrid automatic repeat request

HDL hardware description languages

ID identifier

IE information element

LTE long term evolution

MAC media access control

MCG master cell group

MeNB master evolved node B

MIB master information block

MME mobility management entity

mMTC massive machine type communications

NACK Negative Acknowledgement

NAS non-access stratum

NG CP next generation control plane core

NGC next generation core

NG-C NG-control plane

NG-U NG-user plane

NR MAC new radio MAC

NR PDCP new radio PDCP

NR PHY new radio physical

NR RLC new radio RLC

NR RRC new radio RRC

NR new radio

NSSAI network slice selection assistance information

OFDM orthogonal frequency division multiplexing

PCC primary component carrier

PCell primary cell

PDCCH physical downlink control channel

PDCP packet data convergence protocol

PDU packet data unit

PHICH physical HARQ indicator channel

PHY physical

PLMN public land mobile network

PSCell primary secondary cell

pTAG primary timing advance group

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RA random access

RACH random access channel

RAN radio access network

RAP random access preamble

RAR random access response

RB resource blocks

RBG resource block groups

RLC radio link control

RRC radio resource control

RRM radio resource management

RV redundancy version

SCC secondary component carrier

SCell secondary cell

SCG secondary cell group

SC-OFDM single carrier-OFDM

SDU service data unit

SeNB secondary evolved node B

SFN system frame number

S-GW serving gateway

SIB system information block

SC-OFDM single carrier orthogonal frequency division multiplexing

SRB signaling radio bearer

sTAG(s) secondary timing advance group(s)

TA timing advance

TAG timing advance group

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TTI transmission time interval

TB transport block

UE user equipment

UL uplink

UPGW user plane gateway

URLLC ultra-reliable low-latency communications

VHDL VHSIC hardware description language

Xn-C Xn-control plane

Xn-U Xn-user plane

Xx-C Xx-control plane

Xx-U Xx-user plane

Examples may be implemented using various physical layer modulation andtransmission mechanisms. Example transmission mechanisms may include,but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/orthe like. Hybrid transmission mechanisms such as TDMA/CDMA, andOFDM/CDMA may also be employed. Various modulation schemes may be usedfor signal transmission in the physical layer. Examples of modulationschemes include, but are not limited to: phase, amplitude, code, acombination of these, and/or the like. An example radio transmissionmethod may implement QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM,and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme depending on transmission requirements and radio conditions.

FIG. 1 shows example sets of OFDM subcarriers. As shown in this example,arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDMsystem. The OFDM system may use technology such as OFDM technology,DFTS-OFDM, SC-OFDM technology, or the like. For example, arrow 101 showsa subcarrier transmitting information symbols. FIG. 1 is shown as anexample, and a typical multicarrier OFDM system may include moresubcarriers in a carrier. For example, the number of subcarriers in acarrier may be in the range of 10 to 10,000 subcarriers. FIG. 1 showstwo guard bands 106 and 107 in a transmission band. As shown in FIG. 1,guard band 106 is between subcarriers 103 and subcarriers 104. Theexample set of subcarriers A 102 includes subcarriers 103 andsubcarriers 104. FIG. 1 also shows an example set of subcarriers B 105.As shown, there is no guard band between any two subcarriers in theexample set of subcarriers B 105. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 2 shows an example timing arrangement with transmission time andreception time for two carriers. A multicarrier OFDM communicationsystem may include one or more carriers, for example, ranging from 1 to10 carriers. Carrier A 204 and carrier B 205 may have the same ordifferent timing structures. Although FIG. 2 shows two synchronizedcarriers, carrier A 204 and carrier B 205 may or may not be synchronizedwith each other. Different radio frame structures may be supported forFDD and TDD duplex mechanisms. FIG. 2 shows an example FDD frame timing.Downlink and uplink transmissions may be organized into radio frames201. In this example, radio frame duration is 10 milliseconds (msec).Other frame durations, for example, in the range of 1 to 100 msec mayalso be supported. In this example, each 10 msec radio frame 201 may bedivided into ten equally sized subframes 202. Other subframe durationssuch as including 0.5 msec, 1 msec, 2 msec, and 5 msec may also besupported. Subframe(s) may consist of two or more slots (e.g., slots 206and 207). For the example of FDD, 10 subframes may be available fordownlink transmission and 10 subframes may be available for uplinktransmissions in each 10 msec interval. Uplink and downlinktransmissions may be separated in the frequency domain. A slot may be 7or 14 OFDM symbols for the same subcarrier spacing of up to 60 kHz withnormal CP. A slot may be 14 OFDM symbols for the same subcarrier spacinghigher than 60 kHz with normal CP. A slot may include all downlink, alluplink, or a downlink part and an uplink part, and/or alike. Slotaggregation may be supported, e.g., data transmission may be scheduledto span one or multiple slots. For example, a mini-slot may start at anOFDM symbol in a subframe. A mini-slot may have a duration of one ormore OFDM symbols. Slot(s) may include a plurality of OFDM symbols 203.The number of OFDM symbols 203 in a slot 206 may depend on the cyclicprefix length and subcarrier spacing.

FIG. 3 shows an example of OFDM radio resources, including a resourcegrid structure in time 304 and frequency 305. The quantity of downlinksubcarriers or RBs may depend, at least in part, on the downlinktransmission bandwidth 306 configured in the cell. The smallest radioresource unit may be called a resource element (e.g., 301). Resourceelements may be grouped into resource blocks (e.g., 302). Resourceblocks may be grouped into larger radio resources called Resource BlockGroups (RBG) (e.g., 303). The transmitted signal in slot 206 may bedescribed by one or several resource grids of a plurality of subcarriersand a plurality of OFDM symbols. Resource blocks may be used to describethe mapping of certain physical channels to resource elements. Otherpre-defined groupings of physical resource elements may be implementedin the system depending on the radio technology. For example, 24subcarriers may be grouped as a radio block for a duration of 5 msec. Aresource block may correspond to one slot in the time domain and 180 kHzin the frequency domain (for 15 kHz subcarrier bandwidth and 12subcarriers).

Multiple numerologies may be supported. A numerology may be derived byscaling a basic subcarrier spacing by an integer N. Scalable numerologymay allow at least from 15 kHz to 480 kHz subcarrier spacing. Thenumerology with 15 kHz and scaled numerology with different subcarrierspacing with the same CP overhead may align at a symbol boundary every 1msec in a NR carrier.

FIG. 4 shows hardware elements of a base station 401 and a wirelessdevice 406. A communication network 400 may include at least one basestation 401 and at least one wireless device 406. The base station 401may include at least one communication interface 402, one or moreprocessors 403, and at least one set of program code instructions 405stored in non-transitory memory 404 and executable by the one or moreprocessors 403. The wireless device 406 may include at least onecommunication interface 407, one or more processors 408, and at leastone set of program code instructions 410 stored in non-transitory memory409 and executable by the one or more processors 408. A communicationinterface 402 in the base station 401 may be configured to engage incommunication with a communication interface 407 in the wireless device406, such as via a communication path that includes at least onewireless link 411. The wireless link 411 may be a bi-directional link.The communication interface 407 in the wireless device 406 may also beconfigured to engage in communication with the communication interface402 in the base station 401. The base station 401 and the wirelessdevice 406 may be configured to send and receive data over the wirelesslink 411 using multiple frequency carriers. Base stations, wirelessdevices, and other communication devices may include structure andoperations of transceiver(s). A transceiver is a device that includesboth a transmitter and receiver. Transceivers may be employed in devicessuch as wireless devices, base stations, relay nodes, and/or the like.Examples for radio technology implemented in the communicationinterfaces 402, 407 and the wireless link 411 are shown in FIG. 1, FIG.2, FIG. 3, FIG. 5, and associated text. The communication network 400may comprise any number and/or type of devices, such as, for example,computing devices, wireless devices, mobile devices, handsets, tablets,laptops, internet of things (IoT) devices, hotspots, cellular repeaters,computing devices, and/or, more generally, user equipment (e.g., UE).

Although one or more of the above types of devices may be referencedherein (e.g., UE, wireless device, computing device, etc.), it should beunderstood that any device herein may comprise any one or more of theabove types of devices or similar devices. The communication network400, and any other network referenced herein, may comprise an LTEnetwork, a 5G network, or any other network for wireless communications.

Apparatuses, systems, and/or methods described herein may generally bedescribed as implemented on one or more devices (e.g., wireless device,base station, eNB, gNB, computing device, etc.), in one or morenetworks, but it will be understood that one or more features and stepsmay be implemented on any device and/or in any network. As usedthroughout, the term “base station” may comprise one or more of: a basestation, a node, a Node B, a gNB, an eNB, an ng-eNB, a relay node (e.g.,an integrated access and backhaul (IAB) node), a donor node (e.g., adonor eNB, a donor gNB, etc.), an access point (e.g., a WiFi accesspoint), a computing device, a device capable of wirelesslycommunicating, or any other device capable of sending and/or receivingsignals. As used throughout, the term “wireless device” may comprise oneor more of: a UE, a handset, a mobile device, a computing device, anode, a device capable of wirelessly communicating, or any other devicecapable of sending and/or receiving signals. Any reference to one ormore of these terms/devices also considers use of any other term/devicementioned above.

The communications network 400 may comprise Radio Access Network (RAN)architecture. The RAN architecture may comprise one or more RAN nodesthat may be a next generation Node B (gNB) (e.g., 401) providing NewRadio (NR) user plane and control plane protocol terminations towards afirst wireless device (e.g. 406). A RAN node may be a next generationevolved Node B (ng-eNB), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device. The first wireless device may communicate with agNB over a Uu interface. The second wireless device may communicate witha ng-eNB over a Uu interface. Base station 401 may comprise one or moreof a gNB, ng-eNB, and/or the like.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of wirelessdevices in RRC_INACTIVE state, distribution function for Non-AccessStratum (NAS) messages, RAN sharing, and dual connectivity or tightinterworking between NR and E-UTRA.

One or more gNBs and/or one or more ng-eNBs may be interconnected witheach other by means of Xn interface. A gNB or an ng-eNB may be connectedby means of NG interfaces to 5G Core Network (5GC). 5GC may comprise oneor more AMF/User Plane Function (UPF) functions. A gNB or an ng-eNB maybe connected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g., non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (e.g., NG-C) interface. The NG-C interface may provide functionssuch as NG interface management, UE context management, UE mobilitymanagement, transport of NAS messages, paging, PDU session management,configuration transfer or warning message transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (if applicable), external PDU sessionpoint of interconnect to data network, packet routing and forwarding,packet inspection and user plane part of policy rule enforcement,traffic usage reporting, uplink classifier to support routing trafficflows to a data network, branching point to support multi-homed PDUsession, QoS handling for user plane, e.g. packet filtering, gating,Uplink (UL)/Downlink (DL) rate enforcement, uplink traffic verification(e.g. Service Data Flow (SDF) to QoS flow mapping), downlink packetbuffering and/or downlink data notification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling for mobility between 3^(rd) GenerationPartnership Project (3GPP) access networks, idle mode UE reachability(e.g., control and execution of paging retransmission), registrationarea management, support of intra-system and inter-system mobility,access authentication, access authorization including check of roamingrights, mobility management control (subscription and policies), supportof network slicing and/or Session Management Function (SMF) selection

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or a non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ora non-operational state. In other words, the hardware, software,firmware, registers, memory values, and/or the like may be “configured”within a device, whether the device is in an operational or anonoperational state, to provide the device with specificcharacteristics. Terms such as “a control message to cause in a device”may mean that a control message has parameters that may be used toconfigure specific characteristics in the device, whether the device isin an operational or a non-operational state.

A 5G network may include a multitude of base stations, providing a userplane NR PDCP/NR RLC/NR MAC/NR PHY and control plane (NR RRC) protocolterminations towards the wireless device. The base station(s) may beinterconnected with other base station(s) (e.g., employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B show examplesfor interfaces between a 5G core network (e.g., NGC) and base stations(e.g., gNB and eLTE eNB). For example, the base stations may beinterconnected to the NGC control plane (e.g., NG CP) employing the NG-Cinterface and to the NGC user plane (e.g., UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors, for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g., TAI), and atRRC connection re-establishment/handover, one serving cell may providethe security input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC); in the uplink, thecarrier corresponding to the PCell may be the Uplink Primary ComponentCarrier (UL PCC). Depending on wireless device capabilities, SecondaryCells (SCells) may be configured to form together with the PCell a setof serving cells. In the downlink, the carrier corresponding to an SCellmay be a Downlink Secondary Component Carrier (DL SCC); in the uplink,the carrier corresponding to an SCell may be an Uplink SecondaryComponent Carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context in which it is used). The cell ID may beequally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, reference to a firstphysical cell ID for a first downlink carrier may indicate that thefirst physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.Reference to a first carrier that is activated may indicate that thecell comprising the first carrier is activated.

A device may be configured to operate as needed by freely combining anyof the examples. The disclosed mechanisms may be performed if certaincriteria are met, for example, in a wireless device, a base station, aradio environment, a network, a combination of the above, and/or thelike. Example criteria may be based, at least in part, on for example,traffic load, initial system set up, packet sizes, trafficcharacteristics, a combination of the above, and/or the like. One ormore criteria may be satisfied. It may be possible to implement examplesthat selectively implement disclosed protocols.

A base station may communicate with a variety of wireless devices.Wireless devices may support multiple technologies, and/or multiplereleases of the same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. Referenceto a base station communicating with a plurality of wireless devices mayindicate that a base station may communicate with a subset of the totalwireless devices in a coverage area. A plurality of wireless devices ofa given LTE or 5G release, with a given capability and in a given sectorof the base station, may be used. The plurality of wireless devices mayrefer to a selected plurality of wireless devices, and/or a subset oftotal wireless devices in a coverage area which perform according todisclosed methods, and/or the like. There may be a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices perform based onolder releases of LTE or 5G technology.

A base station may transmit (e.g., to a wireless device) one or moremessages (e.g. RRC messages) that may comprise a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). The other SImay be transmitted via SystemInformationBlockType2. For a wirelessdevice in an RRC_Connected state, dedicated RRC signaling may beemployed for the request and delivery of the other SI. For the wirelessdevice in the RRC_Idle state and/or the RRC_Inactive state, the requestmay trigger a random-access procedure.

A wireless device may send its radio access capability information whichmay be static. A base station may request what capabilities for awireless device to report based on band information. If allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

If CA is configured, a wireless device may have an RRC connection with anetwork. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. If adding a new SCell, dedicatedRRC signaling may be employed to send all required system information ofthe SCell. In connected mode, wireless devices may not need to acquirebroadcasted system information directly from the SCells.

An RRC connection reconfiguration procedure may be used to modify an RRCconnection, (e.g. to establish, modify and/or release RBs, to performhandover, to setup, modify, and/or release measurements, to add, modify,and/or release SCells and cell groups). As part of the RRC connectionreconfiguration procedure, NAS dedicated information may be transferredfrom the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be used to establish (or reestablish, resume) an RRC connection. AnRRC connection establishment procedure may comprise SRB1 establishment.The RRC connection establishment procedure may be used to transfer theinitial NAS dedicated information message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure, e.g., after successful securityactivation. A measurement report message may be employed to transmitmeasurement results.

FIG. 5A, FIG. 5B, FIG. 5C, and FIG. 5D show examples of architecture foruplink and downlink signal transmission. FIG. 5A shows an example for anuplink physical channel.

The baseband signal representing the physical uplink shared channel maybe processed according to the following processes, which may beperformed by structures described below. These structures andcorresponding functions are shown as examples, however, it isanticipated that other structures and/or functions may be implemented invarious examples. The structures and corresponding functions maycomprise, e.g., one or more scrambling devices 501A and 501B configuredto perform scrambling of coded bits in each of the codewords to betransmitted on a physical channel; one or more modulation mappers 502Aand 502B configured to perform modulation of scrambled bits to generatecomplex-valued symbols; a layer mapper 503 configured to perform mappingof the complex-valued modulation symbols onto one or severaltransmission layers; one or more transform precoders 504A and 504B togenerate complex-valued symbols; a precoding device 505 configured toperform precoding of the complex-valued symbols; one or more resourceelement mappers 506A and 506B configured to perform mapping of precodedcomplex-valued symbols to resource elements; one or more signalgenerators 507A and 507B configured to perform the generation of acomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport; and/or the like.

FIG. 5B shows an example for performing modulation and up-conversion tothe carrier frequency of the complex-valued DFTS-OFDM/SC-FDMA basebandsignal, e.g., for each antenna port and/or for the complex-valuedphysical random access channel (PRACH) baseband signal. For example, thebaseband signal, represented as s₁(t), may be split, by a signalsplitter 510, into real and imaginary components, Re{s₁(t)} andIm{s₁(t)}, respectively. The real component may be modulated by amodulator 511A, and the imaginary component may be modulated by amodulator 511B. The output signal of the modulator 511A and the outputsignal of the modulator 511B may be mixed by a mixer 512. The outputsignal of the mixer 512 may be input to a filtering device 513, andfiltering may be employed by the filtering device 513 prior totransmission.

FIG. 5C shows an example structure for downlink transmissions. Thebaseband signal representing a downlink physical channel may beprocessed by the following processes, which may be performed bystructures described below. These structures and corresponding functionsare shown as examples, however, it is anticipated that other structuresand/or functions may be implemented in various examples. The structuresand corresponding functions may comprise, e.g., one or more scramblingdevices 531A and 531B configured to perform scrambling of coded bits ineach of the codewords to be transmitted on a physical channel; one ormore modulation mappers 532A and 532B configured to perform modulationof scrambled bits to generate complex-valued modulation symbols; a layermapper 533 configured to perform mapping of the complex-valuedmodulation symbols onto one or several transmission layers; a precodingdevice 534 configured to perform precoding of the complex-valuedmodulation symbols on each layer for transmission on the antenna ports;one or more resource element mappers 535A and 535B configured to performmapping of complex-valued modulation symbols for each antenna port toresource elements; one or more OFDM signal generators 536A and 536Bconfigured to perform the generation of complex-valued time-domain OFDMsignal for each antenna port; and/or the like.

FIG. 5D shows an example structure for modulation and up-conversion tothe carrier frequency of the complex-valued OFDM baseband signal foreach antenna port. For example, the baseband signal, represented as s₁^((p))(t), may be split, by a signal splitter 520, into real andimaginary components, Re{s₁ ^((p))(t)} and Im{s₁ ^((p))(t)},respectively. The real component may be modulated by a modulator 521A,and the imaginary component may be modulated by a modulator 521B. Theoutput signal of the modulator 521A and the output signal of themodulator 521B may be mixed by a mixer 522. The output signal of themixer 522 may be input to a filtering device 523, and filtering may beemployed by the filtering device 523 prior to transmission.

FIG. 6 and FIG. 7 show examples for protocol structures with CA andmulti-connectivity. NR may support multi-connectivity operation, wherebya multiple receiver/transmitter (RX/TX) wireless device in RRC_CONNECTEDmay be configured to utilize radio resources provided by multipleschedulers located in multiple gNBs connected via a non-ideal or idealbackhaul over the Xn interface. gNBs involved in multi-connectivity fora certain wireless device may assume two different roles: a gNB mayeither act as a master gNB (e.g., 600) or as a secondary gNB (e.g., 610or 620). In multi-connectivity, a wireless device may be connected toone master gNB (e.g., 600) and one or more secondary gNBs (e.g., 610and/or 620). Any one or more of the Master gNB 600 and/or the secondarygNB s 610 and 620 may be a Next Generation (NG) NodeB. The master gNB600 may comprise protocol layers NR MAC 601, NR RLC 602 and 603, and NRPDCP 604 and 605. The secondary gNB may comprise protocol layers NR MAC611, NR RLC 612 and 613, and NR PDCP 614. The secondary gNB may compriseprotocol layers NR MAC 621, NR RLC 622 and 623, and NR PDCP 624. Themaster gNB 600 may communicate via an interface 606 and/or via aninterface 607, the secondary gNB 610 may communicate via an interface615, and the secondary gNB 620 may communicate via an interface 625. Themaster gNB 600 may also communicate with the secondary gNB 610 and thesecondary gNB 621 via interfaces 608 and 609, respectively, which mayinclude Xn interfaces. For example, the master gNB 600 may communicatevia the interface 608, at layer NR PDCP 605, and with the secondary gNB610 at layer NR RLC 612. The master gNB 600 may communicate via theinterface 609, at layer NR PDCP 605, and with the secondary gNB 620 atlayer NR RLC 622.

FIG. 7 shows an example structure for the UE side MAC entities, e.g., ifa Master Cell Group (MCG) and a Secondary Cell Group (SCG) areconfigured. Media Broadcast Multicast Service (MBMS) reception may beincluded but is not shown in this figure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is set up. As an example, threealternatives may exist, an MCG bearer, an SCG bearer, and a splitbearer, such as shown in FIG. 6. NR RRC may be located in a master gNBand SRBs may be configured as a MCG bearer type and may use the radioresources of the master gNB. Multi-connectivity may have at least onebearer configured to use radio resources provided by the secondary gNB.Multi-connectivity may or may not be configured or implemented.

For multi-connectivity, the wireless device may be configured withmultiple NR MAC entities: e.g., one NR MAC entity for a master gNB, andother NR MAC entities for secondary gNBs. In multi-connectivity, theconfigured set of serving cells for a wireless device may comprise twosubsets: e.g., the Master Cell Group (MCG) including the serving cellsof the master gNB, and the Secondary Cell Groups (SCGs) including theserving cells of the secondary gNBs.

At least one cell in a SCG may have a configured UL component carrier(CC) and one of the UL CCs, e.g., named PSCell (or PCell of SCG, orsometimes called PCell), may be configured with PUCCH resources. If theSCG is configured, there may be at least one SCG bearer or one splitbearer. If a physical layer problem or a random access problem on aPSCell occurs or is detected, if the maximum number of NR RLCretransmissions has been reached associated with the SCG, or if anaccess problem on a PSCell during a SCG addition or a SCG change occursor is detected, then an RRC connection re-establishment procedure maynot be triggered, UL transmissions towards cells of the SCG may bestopped, a master gNB may be informed by the wireless device of a SCGfailure type, and for a split bearer the DL data transfer over themaster gNB may be maintained. The NR RLC Acknowledge Mode (AM) bearermay be configured for the split bearer. Like the PCell, a PSCell may notbe de-activated. The PSCell may be changed with an SCG change (e.g.,with a security key change and a RACH procedure). A direct bearer typemay change between a split bearer and an SCG bearer, or a simultaneousconfiguration of an SCG and a split bearer may or may not be supported.

A master gNB and secondary gNBs may intreract for multi-connectivity.The master gNB may maintain the RRM measurement configuration of thewireless device, and the master gNB may, (e.g., based on receivedmeasurement reports, and/or based on traffic conditions and/or bearertypes), decide to ask a secondary gNB to provide additional resources(e.g., serving cells) for a wireless device. If a request from themaster gNB is received, a secondary gNB may create a container that mayresult in the configuration of additional serving cells for the wirelessdevice (or the secondary gNB decide that it has no resource available todo so). For wireless device capability coordination, the master gNB mayprovide some or all of the Active Set (AS) configuration and thewireless device capabilities to the secondary gNB. The master gNB andthe secondary gNB may exchange information about a wireless deviceconfiguration, such as by employing NR RRC containers (e.g., inter-nodemessages) carried in Xn messages. The secondary gNB may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary gNB). The secondary gNB may decide which cell is the PSCellwithin the SCG. The master gNB may or may not change the content of theNR RRC configuration provided by the secondary gNB. In an SCG additionand an SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s). Both a master gNB and asecondary gNBs may know the system frame number (SFN) and subframeoffset of each other by operations, administration, and maintenance(OAM) (e.g., for the purpose of discontinuous reception (DRX) alignmentand identification of a measurement gap). If adding a new SCG SCell,dedicated NR RRC signaling may be used for sending required systeminformation of the cell for CA, except, e.g., for the SFN acquired froman MIB of the PSCell of an SCG.

FIG. 7 shows an example of dual-connectivity (DC) for two MAC entitiesat a wireless device side. A first MAC entity may comprise a lower layerof an MCG 700, an upper layer of an MCG 718, and one or moreintermediate layers of an MCG 719. The lower layer of the MCG 700 maycomprise, e.g., a paging channel (PCH) 701, a broadcast channel (BCH)702, a downlink shared channel (DL-SCH) 703, an uplink shared channel(UL-SCH) 704, and a random access channel (RACH) 705. The one or moreintermediate layers of the MCG 719 may comprise, e.g., one or morehybrid automatic repeat request (HARQ) processes 706, one or more randomaccess control processes 707, multiplexing and/or de-multiplexingprocesses 709, logical channel prioritization on the uplink processes710, and a control processes 708 providing control for the aboveprocesses in the one or more intermediate layers of the MCG 719. Theupper layer of the MCG 718 may comprise, e.g., a paging control channel(PCCH) 711, a broadcast control channel (BCCH) 712, a common controlchannel (CCCH) 713, a dedicated control channel (DCCH) 714, a dedicatedtraffic channel (DTCH) 715, and a MAC control 716.

A second MAC entity may comprise a lower layer of an SCG 720, an upperlayer of an SCG 738, and one or more intermediate layers of an SCG 739.The lower layer of the SCG 720 may comprise, e.g., a BCH 722, a DL-SCH723, an UL-SCH 724, and a RACH 725. The one or more intermediate layersof the SCG 739 may comprise, e.g., one or more HARQ processes 726, oneor more random access control processes 727, multiplexing and/orde-multiplexing processes 729, logical channel prioritization on theuplink processes 730, and a control processes 728 providing control forthe above processes in the one or more intermediate layers of the SCG739. The upper layer of the SCG 738 may comprise, e.g., a BCCH 732, aDCCH 714, a DTCH 735, and a MAC control 736.

Serving cells may be grouped in a TA group (TAG). Serving cells in oneTAG may use the same timing reference. For a given TAG, a wirelessdevice may use at least one downlink carrier as a timing reference. Fora given TAG, a wireless device may synchronize uplink subframe and frametransmission timing of uplink carriers belonging to the same TAG.Serving cells having an uplink to which the same TA applies maycorrespond to serving cells hosted by the same receiver. A wirelessdevice supporting multiple TAs may support two or more TA groups. One TAgroup may include the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not include thePCell and may be called a secondary TAG (sTAG). Carriers within the sameTA group may use the same TA value and/or the same timing reference. IfDC is configured, cells belonging to a cell group (e.g., MCG or SCG) maybe grouped into multiple TAGs including a pTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations. In Example 1, a pTAG comprisesa PCell, and an sTAG comprises an SCell1. In Example 2, a pTAG comprisesa PCell and an SCell1, and an sTAG comprises an SCell2 and an SCell3. InExample 3, a pTAG comprises a PCell and an SCell1, and an sTAG1comprises an SCell2 and an SCell3, and an sTAG2 comprises a SCell4. Upto four TAGs may be supported in a cell group (MCG or SCG), and otherexample TAG configurations may also be provided. In various examples,structures and operations are described for use with a pTAG and an sTAG.Some of the examples may be used for configurations with multiple sTAGs.

An eNB may initiate an RA procedure, via a PDCCH order, for an activatedSCell. The PDCCH order may be sent on a scheduling cell of this SCell.If cross carrier scheduling is configured for a cell, the schedulingcell may be different than the cell that is employed for preambletransmission, and the PDCCH order may include an SCell index. At least anon-contention based RA procedure may be supported for SCell(s) assignedto sTAG(s).

FIG. 9 shows an example of random access processes, and a correspondingmessage flow, in a secondary TAG. A base station, such as an eNB, maytransmit an activation command 900 to a wireless device, such as a UE.The activation command 900 may be transmitted to activate an SCell. Thebase station may also transmit a PDDCH order 901 to the wireless device,which may be transmitted, e.g., after the activation command 900. Thewireless device may begin to perform a RACH process for the SCell, whichmay be initiated, e.g., after receiving the PDDCH order 901. A wirelessdevice may transmit to the base station (e.g., as part of a RACHprocess) a preamble 902 (e.g., Msg1), such as a random access preamble(RAP). The preamble 902 may be transmitted in response to the PDCCHorder 901. The wireless device may transmit the preamble 902 via anSCell belonging to an sTAG. Preamble transmission for SCells may becontrolled by a network using PDCCH format 1A. The base station may senda random access response (RAR) 903 (e.g., Msg2 message) to the wirelessdevice. The RAR 903 may be in response to the preamble 902 transmissionvia the SCell. The RAR 903 may be addressed to a random access radionetwork temporary identifier (RA-RNTI) in a PCell common search space(CSS). If the wireless device receives the RAR 903, the RACH process mayconclude. The RACH process may conclude, e.g., after or in response tothe wireless device receiving the RAR 903 from the base station. Afterthe RACH process, the wireless device may transmit an uplinktransmission 904. The uplink transmission 904 may comprise uplinkpackets transmitted via the same SCell used for the preamble 902transmission.

Initial timing alignment for communications between the wireless deviceand the base station may be performed through a random access procedure,such as described above regarding FIG. 9. The random access proceduremay involve a wireless device, such as a UE, transmitting a randomaccess preamble and a base station, such as an eNB, responding with aninitial TA command NTA (amount of timing advance) within a random accessresponse window. The start of the random access preamble may be alignedwith the start of a corresponding uplink subframe at the wireless deviceassuming NTA=0. The eNB may estimate the uplink timing from the randomaccess preamble transmitted by the wireless device. The TA command maybe derived by the eNB based on the estimation of the difference betweenthe desired UL timing and the actual UL timing. The wireless device maydetermine the initial uplink transmission timing relative to thecorresponding downlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. If an eNB performs anSCell addition configuration, the related TAG configuration may beconfigured for the SCell. An eNB may modify the TAG configuration of anSCell by removing (e.g., releasing) the SCell and adding (e.g.,configuring) a new SCell (with the same physical cell ID and frequency)with an updated TAG ID. The new SCell with the updated TAG ID mayinitially be inactive subsequent to being assigned the updated TAG ID.The eNB may activate the updated new SCell and start scheduling packetson the activated SCell. In some examples, it may not be possible tochange the TAG associated with an SCell, but rather, the SCell may needto be removed and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, such as at least one RRC reconfiguration message,may be sent to the wireless device. The at least one RRC message may besent to the wireless device to reconfigure TAG configurations, e.g., byreleasing the SCell and configuring the SCell as a part of the pTAG. If,e.g., an SCell is added or configured without a TAG index, the SCell maybe explicitly assigned to the pTAG. The PCell may not change its TAgroup and may be a member of the pTAG.

In LTE Release-10 and Release-11 CA, a PUCCH transmission is onlytransmitted on a PCell (e.g., a PSCell) to an eNB. In LTE-Release 12 andearlier, a wireless device may transmit PUCCH information on one cell(e.g., a PCell or a PSCell) to a given eNB. As the number of CA capablewireless devices increase, and as the number of aggregated carriersincrease, the number of PUCCHs and the PUCCH payload size may increase.Accommodating the PUCCH transmissions on the PCell may lead to a highPUCCH load on the PCell. A PUCCH on an SCell may be used to offload thePUCCH resource from the PCell. More than one PUCCH may be configured.For example, a PUCCH on a PCell may be configured and another PUCCH onan SCell may be configured. One, two, or more cells may be configuredwith PUCCH resources for transmitting CSI, acknowledgment (ACK), and/ornon-acknowledgment (NACK) to a base station. Cells may be grouped intomultiple PUCCH groups, and one or more cell within a group may beconfigured with a PUCCH. In some examples, one SCell may belong to onePUCCH group. SCells with a configured PUCCH transmitted to a basestation may be called a PUCCH SCell, and a cell group with a commonPUCCH resource transmitted to the same base station may be called aPUCCH group.

A MAC entity may have a configurable timer, e.g., timeAlignmentTimer,per TAG. The timeAlignmentTimer may be used to control how long the MACentity considers the serving cells belonging to the associated TAG to beuplink time aligned. If a Timing Advance Command MAC control element isreceived, the MAC entity may apply the Timing Advance Command for theindicated TAG; and/or the MAC entity may start or restart thetimeAlignmentTimer associated with a TAG that may be indicated by theTiming Advance Command MAC control element. If a Timing Advance Commandis received in a Random Access Response message for a serving cellbelonging to a TAG, the MAC entity may apply the Timing Advance Commandfor this TAG and/or start or restart the timeAlignmentTimer associatedwith this TAG. Additionally or alternatively, if the Random AccessPreamble is not selected by the MAC entity, the MAC entity may apply theTiming Advance Command for this TAG and/or start or restart thetimeAlignmentTimer associated with this TAG. If the timeAlignmentTimerassociated with this TAG is not running, the Timing Advance Command forthis TAG may be applied, and the timeAlignmentTimer associated with thisTAG may be started. If the contention resolution is not successful, atimeAlignmentTimer associated with this TAG may be stopped. If thecontention resolution is successful, the MAC entity may ignore thereceived Timing Advance Command. The MAC entity may determine whetherthe contention resolution is successful or whether the contentionresolution is not successful.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork (e.g., NGC) and base stations (e.g., gNB and eLTE eNB). A basestation, such as a gNB 1020, may be interconnected to an NGC 1010control plane employing an NG-C interface. The base station, e.g., thegNB 1020, may also be interconnected to an NGC 1010 user plane (e.g.,UPGW) employing an NG-U interface. As another example, a base station,such as an eLTE eNB 1040, may be interconnected to an NGC 1030 controlplane employing an NG-C interface. The base station, e.g., the eLTE eNB1040, may also be interconnected to an NGC 1030 user plane (e.g., UPGW)employing an NG-U interface. An NG interface may support a many-to-manyrelation between 5G core networks and base stations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexamples for architectures of tight interworking between a 5G RAN and anLTE RAN. The tight interworking may enable a multiplereceiver/transmitter (RX/TX) wireless device in an RRC_CONNECTED stateto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g., an eLTE eNB and a gNB). The two basestations may be connected via a non-ideal or ideal backhaul over the Xxinterface between an LTE eNB and a gNB, or over the Xn interface betweenan eLTE eNB and a gNB. Base stations involved in tight interworking fora certain wireless device may assume different roles. For example, abase station may act as a master base station or a base station may actas a secondary base station. In tight interworking, a wireless devicemay be connected to both a master base station and a secondary basestation. Mechanisms implemented in tight interworking may be extended tocover more than two base stations.

A master base station may be an LTE eNB 1102A or an LTE eNB 1102B, whichmay be connected to EPC nodes 1101A or 1101B, respectively. Thisconnection to EPC nodes may be, e.g., to an MME via the S1-C interfaceand/or to an S-GW via the S1-U interface. A secondary base station maybe a gNB 1103A or a gNB 1103B, either or both of which may be anon-standalone node having a control plane connection via an Xx-Cinterface to an LTE eNB (e.g., the LTE eNB 1102A or the LTE eNB 1102B).In the tight interworking architecture of FIG. 11A, a user plane for agNB (e.g., the gNB 1103A) may be connected to an S-GW (e.g., the EPC1101A) through an LTE eNB (e.g., the LTE eNB 1102A), via an Xx-Uinterface between the LTE eNB and the gNB, and via an S1-U interfacebetween the LTE eNB and the S-GW. In the architecture of FIG. 11B, auser plane for a gNB (e.g., the gNB 1103B) may be connected directly toan S-GW (e.g., the EPC 1101B) via an S1-U interface between the gNB andthe S-GW.

A master base station may be a gNB 1103C or a gNB 1103D, which may beconnected to NGC nodes 1101C or 1101D, respectively. This connection toNGC nodes may be, e.g., to a control plane core node via the NG-Cinterface and/or to a user plane core node via the NG-U interface. Asecondary base station may be an eLTE eNB 1102C or an eLTE eNB 1102D,either or both of which may be a non-standalone node having a controlplane connection via an Xn-C interface to a gNB (e.g., the gNB 1103C orthe gNB 1103D). In the tight interworking architecture of FIG. 11C, auser plane for an eLTE eNB (e.g., the eLTE eNB 1102C) may be connectedto a user plane core node (e.g., the NGC 1101C) through a gNB (e.g., thegNB 1103C), via an Xn-U interface between the eLTE eNB and the gNB, andvia an NG-U interface between the gNB and the user plane core node. Inthe architecture of FIG. 11D, a user plane for an eLTE eNB (e.g., theeLTE eNB 1102D) may be connected directly to a user plane core node(e.g., the NGC 1101D) via an NG-U interface between the eLTE eNB and theuser plane core node.

A master base station may be an eLTE eNB 1102E or an eLTE eNB 1102F,which may be connected to NGC nodes 1101E or 1101F, respectively. Thisconnection to NGC nodes may be, e.g., to a control plane core node viathe NG-C interface and/or to a user plane core node via the NG-Uinterface. A secondary base station may be a gNB 1103E or a gNB 1103F,either or both of which may be a non-standalone node having a controlplane connection via an Xn-C interface to an eLTE eNB (e.g., the eLTEeNB 1102E or the eLTE eNB 1102F). In the tight interworking architectureof FIG. 11E, a user plane for a gNB (e.g., the gNB 1103E) may beconnected to a user plane core node (e.g., the NGC 1101E) through aneLTE eNB (e.g., the eLTE eNB 1102E), via an Xn-U interface between theeLTE eNB and the gNB, and via an NG-U interface between the eLTE eNB andthe user plane core node. In the architecture of FIG. 11F, a user planefor a gNB (e.g., the gNB 1103F) may be connected directly to a userplane core node (e.g., the NGC 1101F) via an NG-U interface between thegNB and the user plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are examples for radio protocolstructures of tight interworking bearers.

An LTE eNB 1201A may be an S1 master base station, and a gNB 1210A maybe an S1 secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The LTE eNB1201A may be connected to an EPC with a non-standalone gNB 1210A, via anXx interface between the PDCP 1206A and an NR RLC 1212A. The LTE eNB1201A may include protocol layers MAC 1202A, RLC 1203A and RLC 1204A,and PDCP 1205A and PDCP 1206A. An MCG bearer type may interface with thePDCP 1205A, and a split bearer type may interface with the PDCP 1206A.The gNB 1210A may include protocol layers NR MAC 1211A, NR RLC 1212A andNR RLC 1213A, and NR PDCP 1214A. An SCG bearer type may interface withthe NR PDCP 1214A.

A gNB 1201B may be an NG master base station, and an eLTE eNB 1210B maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The gNB1201B may be connected to an NGC with a non-standalone eLTE eNB 1210B,via an Xn interface between the NR PDCP 1206B and an RLC 1212B. The gNB1201B may include protocol layers NR MAC 1202B, NR RLC 1203B and NR RLC1204B, and NR PDCP 1205B and NR PDCP 1206B. An MCG bearer type mayinterface with the NR PDCP 1205B, and a split bearer type may interfacewith the NR PDCP 1206B. The eLTE eNB 1210B may include protocol layersMAC 1211B, RLC 1212B and RLC 1213B, and PDCP 1214B. An SCG bearer typemay interface with the PDCP 1214B.

An eLTE eNB 1201C may be an NG master base station, and a gNB 1210C maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The eLTE eNB1201C may be connected to an NGC with a non-standalone gNB 1210C, via anXn interface between the PDCP 1206C and an NR RLC 1212C. The eLTE eNB1201C may include protocol layers MAC 1202C, RLC 1203C and RLC 1204C,and PDCP 1205C and PDCP 1206C. An MCG bearer type may interface with thePDCP 1205C, and a split bearer type may interface with the PDCP 1206C.The gNB 1210C may include protocol layers NR MAC 1211C, NR RLC 1212C andNR RLC 1213C, and NR PDCP 1214C. An SCG bearer type may interface withthe NR PDCP 1214C.

In a 5G network, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. At least threealternatives may exist, e.g., an MCG bearer, an SCG bearer, and a splitbearer, such as shown in FIG. 12A, FIG. 12B, and FIG. 12C. The NR RRCmay be located in a master base station, and the SRBs may be configuredas an MCG bearer type and may use the radio resources of the master basestation. Tight interworking may have at least one bearer configured touse radio resources provided by the secondary base station. Tightinterworking may or may not be configured or implemented.

The wireless device may be configured with two MAC entities: e.g., oneMAC entity for a master base station, and one MAC entity for a secondarybase station. In tight interworking, the configured set of serving cellsfor a wireless device may comprise of two subsets: e.g., the Master CellGroup (MCG) including the serving cells of the master base station, andthe Secondary Cell Group (SCG) including the serving cells of thesecondary base station.

At least one cell in a SCG may have a configured UL CC and one of them,e.g., a PSCell (or the PCell of the SCG, which may also be called aPCell), is configured with PUCCH resources. If the SCG is configured,there may be at least one SCG bearer or one split bearer. If one or moreof a physical layer problem or a random access problem is detected on aPSCell, if the maximum number of (NR) RLC retransmissions associatedwith the SCG has been reached, and/or if an access problem on a PSCellduring an SCG addition or during an SCG change is detected, then: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of the SCG may be stopped, a master basestation may be informed by the wireless device of a SCG failure type,and/or for a split bearer the DL data transfer over the master basestation may be maintained. The RLC AM bearer may be configured for thesplit bearer. Like the PCell, a PSCell may not be de-activated. A PSCellmay be changed with an SCG change, e.g., with security key change and aRACH procedure. A direct bearer type change, between a split bearer andan SCG bearer, may not be supported. Simultaneous configuration of anSCG and a split bearer may not be supported.

A master base station and a secondary base station may interact. Themaster base station may maintain the RRM measurement configuration ofthe wireless device. The master base station may determine to ask asecondary base station to provide additional resources (e.g., servingcells) for a wireless device. This determination may be based on, e.g.,received measurement reports, traffic conditions, and/or bearer types.If a request from the master base station is received, a secondary basestation may create a container that may result in the configuration ofadditional serving cells for the wireless device, or the secondary basestation may determine that it has no resource available to do so. Themaster base station may provide at least part of the AS configurationand the wireless device capabilities to the secondary base station,e.g., for wireless device capability coordination.

The master base station and the secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried in Xn or Xx messages. Thesecondary base station may initiate a reconfiguration of its existingserving cells (e.g., PUCCH towards the secondary base station). Thesecondary base station may determine which cell is the PSCell within theSCG. The master base station may not change the content of the RRCconfiguration provided by the secondary base station. If an SCG is addedand/or an SCG SCell is added, the master base station may provide thelatest measurement results for the SCG cell(s). Either or both of amaster base station and a secondary base station may know the SFN andsubframe offset of each other by OAM, (e.g., for the purpose of DRXalignment and identification of a measurement gap). If a new SCG SCellis added, dedicated RRC signaling may be used for sending requiredsystem information of the cell, such as for CA, except, e.g., for theSFN acquired from an MIB of the PSCell of an SCG.

FIG. 13A and FIG. 13B show examples for gNB deployment. A core 1301 anda core 1310 may interface with other nodes via RAN-CN interfaces. In anon-centralized deployment example, the full protocol stack (e.g., NRRRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported at one node,such as a gNB 1302, a gNB 1303, and/or an eLTE eNB or LTE eNB 1304.These nodes (e.g., the gNB 1302, the gNB 1303, and the eLTE eNB or LTEeNB 1304) may interface with one of more of each other via a respectiveinter-BS interface. In a centralized deployment example, upper layers ofa gNB may be located in a Central Unit (CU) 1311, and lower layers ofthe gNB may be located in Distributed Units (DU) 1312, 1313, and 1314.The CU-DU interface (e.g., Fs interface) connecting CU 1311 and DUs1312, 1312, and 1314 may be ideal or non-ideal. The Fs-C may provide acontrol plane connection over the Fs interface, and the Fs-U may providea user plane connection over the Fs interface. In the centralizeddeployment, different functional split options between the CU 1311 andthe DUs 1312, 1313, and 1314 may be possible by locating differentprotocol layers (e.g., RAN functions) in the CU 1311 and in the DU 1312,1313, and 1314. The functional split may support flexibility to move theRAN functions between the CU 1311 and the DUs 1312, 1313, and 1314depending on service requirements and/or network environments. Thefunctional split option may change during operation (e.g., after the Fsinterface setup procedure), or the functional split option may changeonly in the Fs setup procedure (e.g., the functional split option may bestatic during operation after Fs setup procedure).

FIG. 14 shows examples for different functional split options of acentralized gNB deployment. Element numerals that are followed by “A” or“B” designations in FIG. 14 may represent the same elements in differenttraffic flows, e.g., either receiving data (e.g., data 1402A) or sendingdata (e.g., 1402B). In the split option example 1, an NR RRC 1401 may bein a CU, and an NR PDCP 1403, an NR RLC (e.g., comprising a High NR RLC1404 and/or a Low NR RLC 1405), an NR MAC (e.g., comprising a High NRMAC 1406 and/or a Low NR MAC 1407), an NR PHY (e.g., comprising a HighNR PHY 1408 and/or a LOW NR PHY 1409), and an RF 1410 may be in a DU. Inthe split option example 2, the NR RRC 1401 and the NR PDCP 1403 may bein a CU, and the NR RLC, the NR MAC, the NR PHY, and the RF 1410 may bein a DU. In the split option example 3, the NR RRC 1401, the NR PDCP1403, and a partial function of the NR RLC (e.g., the High NR RLC 1404)may be in a CU, and the other partial function of the NR RLC (e.g., theLow NR RLC 1405), the NR MAC, the NR PHY, and the RF 1410 may be in aDU. In the split option example 4, the NR RRC 1401, the NR PDCP 1403,and the NR RLC may be in a CU, and the NR MAC, the NR PHY, and the RF1410 may be in a DU. In the split option example 5, the NR RRC 1401, theNR PDCP 1403, the NR RLC, and a partial function of the NR MAC (e.g.,the High NR MAC 1406) may be in a CU, and the other partial function ofthe NR MAC (e.g., the Low NR MAC 1407), the NR PHY, and the RF 1410 maybe in a DU. In the split option example 6, the NR RRC 1401, the NR PDCP1403, the NR RLC, and the NR MAC may be in CU, and the NR PHY and the RF1410 may be in a DU. In the split option example 7, the NR RRC 1401, theNR PDCP 1403, the NR RLC, the NR MAC, and a partial function of the NRPHY (e.g., the High NR PHY 1408) may be in a CU, and the other partialfunction of the NR PHY (e.g., the Low NR PHY 1409) and the RF 1410 maybe in a DU. In the split option example 8, the NR RRC 1401, the NR PDCP1403, the NR RLC, the NR MAC, and the NR PHY may be in a CU, and the RF1410 may be in a DU.

The functional split may be configured per CU, per DU, per wirelessdevice, per bearer, per slice, and/or with other granularities. In a perCU split, a CU may have a fixed split, and DUs may be configured tomatch the split option of the CU. In a per DU split, each DU may beconfigured with a different split, and a CU may provide different splitoptions for different DUs. In a per wireless device split, a gNB (e.g.,a CU and a DU) may provide different split options for differentwireless devices. In a per bearer split, different split options may beutilized for different bearer types. In a per slice splice, differentsplit options may be applied for different slices.

A new radio access network (new RAN) may support different networkslices, which may allow differentiated treatment customized to supportdifferent service requirements with end to end scope. The new RAN mayprovide a differentiated handling of traffic for different networkslices that may be pre-configured, and the new RAN may allow a singleRAN node to support multiple slices. The new RAN may support selectionof a RAN part for a given network slice, e.g., by one or more sliceID(s) or NSSAI(s) provided by a wireless device or provided by an NGC(e.g., an NG CP). The slice ID(s) or NSSAI(s) may identify one or moreof pre-configured network slices in a PLMN. For an initial attach, awireless device may provide a slice ID and/or an NSSAI, and a RAN node(e.g., a gNB) may use the slice ID or the NSSAI for routing an initialNAS signaling to an NGC control plane function (e.g., an NG CP). If awireless device does not provide any slice ID or NSSAI, a RAN node maysend a NAS signaling to a default NGC control plane function.

For subsequent accesses, the wireless device may provide a temporary IDfor a slice identification, which may be assigned by the NGC controlplane function, to enable a RAN node to route the NAS message to arelevant NGC control plane function. The new RAN may support resourceisolation between slices. If the RAN resource isolation is implemented,shortage of shared resources in one slice does not cause a break in aservice level agreement for another slice.

The amount of data traffic carried over networks is expected to increasefor many years to come. The number of users and/or devices is increasingand each user/device accesses an increasing number and variety ofservices, e.g., video delivery, large files, and images. This requiresnot only high capacity in the network, but also provisioning very highdata rates to meet customers' expectations on interactivity andresponsiveness. More spectrum may be required for network operators tomeet the increasing demand. Considering user expectations of high datarates along with seamless mobility, it is beneficial that more spectrumbe made available for deploying macro cells as well as small cells forcommunication systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, if present, may be an effectivecomplement to licensed spectrum for network operators, e.g., to helpaddress the traffic explosion in some examples, such as hotspot areas.Licensed Assisted Access (LAA) offers an alternative for operators tomake use of unlicensed spectrum, e.g., if managing one radio network,offering new possibilities for optimizing the network's efficiency.

Listen-before-talk (clear channel assessment) may be implemented fortransmission in an LAA cell. In a listen-before-talk (LBT) procedure,equipment may apply a clear channel assessment (CCA) check before usingthe channel. For example, the CCA may utilize at least energy detectionto determine the presence or absence of other signals on a channel todetermine if a channel is occupied or clear, respectively. For example,European and Japanese regulations mandate the usage of LBT in theunlicensed bands. Apart from regulatory requirements, carrier sensingvia LBT may be one way for fair sharing of the unlicensed spectrum.

Discontinuous transmission on an unlicensed carrier with limited maximumtransmission duration may be enabled. Some of these functions may besupported by one or more signals to be transmitted from the beginning ofa discontinuous LAA downlink transmission. Channel reservation may beenabled by the transmission of signals, by an LAA node, after gainingchannel access, e.g., via a successful LBT operation, so that othernodes that receive the transmitted signal with energy above a certainthreshold sense the channel to be occupied. Functions that may need tobe supported by one or more signals for LAA operation with discontinuousdownlink transmission may include one or more of the following:detection of the LAA downlink transmission (including cellidentification) by wireless devices, time synchronization of wirelessdevices, and frequency synchronization of wireless devices.

DL LAA design may employ subframe boundary alignment according to LTE-Acarrier aggregation timing relationships across serving cells aggregatedby CA. This may not indicate that the eNB transmissions may start onlyat the subframe boundary. LAA may support transmitting PDSCH if not allOFDM symbols are available for transmission in a subframe according toLBT. Delivery of necessary control information for the PDSCH may also besupported.

LBT procedures may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum may require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. Nodes may follow such regulatory requirements. Anode may optionally use a lower threshold for energy detection than thatspecified by regulatory requirements. LAA may employ a mechanism toadaptively change the energy detection threshold, e.g., LAA may employ amechanism to adaptively lower the energy detection threshold from anupper bound. Adaptation mechanism may not preclude static or semi-staticsetting of the threshold. A Category 4 LBT mechanism or other type ofLBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. For some signals, insome implementation scenarios, in some situations, and/or in somefrequencies, no LBT procedure may performed by the transmitting entity.For example, Category 2 (e.g., LBT without random back-off) may beimplemented. The duration of time that the channel is sensed to be idlebefore the transmitting entity transmits may be deterministic. Forexample, Category 3 (e.g., LBT with random back-off with a contentionwindow of fixed size) may be implemented. The LBT procedure may have thefollowing procedure as one of its components. The transmitting entitymay draw a random number N within a contention window. The size of thecontention window may be specified by the minimum and maximum value ofN. The size of the contention window may be fixed. The random number Nmay be employed in the LBT procedure to determine the duration of timethat the channel is sensed to be idle, e.g., before the transmittingentity transmits on the channel. For example, Category 4 (e.g., LBT withrandom back-off with a contention window of variable size) may beimplemented. The transmitting entity may draw a random number N within acontention window. The size of contention window may be specified by theminimum and maximum value of N. The transmitting entity may vary thesize of the contention window if drawing the random number N. The randomnumber N may be used in the LBT procedure to determine the duration oftime that the channel is sensed to be idle, e.g., before thetransmitting entity transmits on the channel.

LAA may employ uplink LBT at the wireless device. The UL LBT scheme maybe different from the DL LBT scheme, e.g., by using different LBTmechanisms or parameters. These differences in schemes may be due to theLAA UL being based on scheduled access, which may affect a wirelessdevice's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme may include, but are not limitedto, multiplexing of multiple wireless devices in a single subframe.

A DL transmission burst may be a continuous transmission from a DLtransmitting node, e.g., with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from awireless device perspective may be a continuous transmission from awireless device, e.g., with no transmission immediately before or afterfrom the same wireless device on the same CC. A UL transmission burstmay be defined from a wireless device perspective or from an eNBperspective. If an eNB is operating DL and UL LAA over the sameunlicensed carrier, DL transmission burst(s) and UL transmissionburst(s) on LAA may be scheduled in a TDM manner over the sameunlicensed carrier. An instant in time may be part of a DL transmissionburst or part of an UL transmission burst.

A base station may transmit a plurality of beams to a wireless device. Aserving beam may be determined, from the plurality of beams, for thewireless communications between the base station and the wirelessdevice. One or more candidate beams may also be determined, from theplurality of beams, for providing the wireless communications if a beamfailure event occurs, e.g., such that the serving beam becomes unable toprovide the desired communications. One or more candidate beams may bedetermined by a wireless device and/or by a base station. By determiningand configuring a candidate beam, the wireless device and base stationmay continue wireless communications if the serving beam experiences abeam failure event.

Single beam and multi-beam operations may be supported, e.g., in a NR(New Radio) system. In a multi-beam example, a base station (e.g., a gNBin NR) may perform a downlink beam sweep to provide coverage for DLsynchronization signals (SSs) and common control channels. Wirelessdevices may perform uplink beam sweeps for UL direction to access acell. In a single beam example, a base station may configuretime-repetition within one synchronization signal (SS) block. Thistime-repetition may comprise, e.g., one or more of a primarysynchronization signal (PSS), a secondary synchronization signal (SSS),and a physical broadcast channel (PBCH). These signals may be in a widebeam. In a multi-beam examples, a base station may configure one or moreof these signals and physical channels, such as an SS Block, in multiplebeams. A wireless device may identify, e.g., from an SS block, an OFDMsymbol index, a slot index in a radio frame, and a radio frame number.

In an RRC_INACTIVE state or in an RRC_IDLE state, a wireless device mayassume that SS blocks form an SS burst and an SS burst set. An SS burstset may have a given periodicity. SS blocks may be transmitted togetherin multiple beams (e.g., in multiple beam examples) to form an SS burst.One or more SS blocks may be transmitted via one beam. A beam may have asteering direction. If multiple SS bursts transmit beams, these SSbursts together may form an SS burst set, such as shown in FIG. 15. Abase station 1501 (e.g., a gNB in NR) may transmit SS bursts 1502A to1502H during time periods 1503. A plurality of these SS bursts maycomprise an SS burst set, such as an SS burst set 1504 (e.g., SS bursts1502A and 1502E). An SS burst set may comprise any number of a pluralityof SS bursts 1502A to 1502H. Each SS burst within an SS burst set maytransmitted at a fixed or variable periodicity during time periods 1503.

In a multi-beam example, one or more of PSS, SSS, or PBCH signals may berepeated for a cell, e.g., to support cell selection, cell reselection,and/or initial access procedures. For an SS burst, an associated PBCH ora physical downlink shared channel (PDSCH) scheduling system informationmay be broadcasted by a base station to multiple wireless devices. ThePDSCH may be indicated by a physical downlink control channel (PDCCH) ina common search space. The system information may comprise systeminformation block type 2 (SIB2). SIB2 may carry a physical random accesschannel (PRACH) configuration for a beam. For a beam, a base station(e.g., a gNB in NR) may have a RACH configuration which may include aPRACH preamble pool, time and/or frequency radio resources, and otherpower related parameters. A wireless device may use a PRACH preamblefrom a RACH configuration to initiate a contention-based RACH procedureor a contention-free RACH procedure. A wireless device may perform a4-step RACH procedure, which may be a contention-based RACH procedure ora contention-free RACH procedure. The wireless device may select a beamassociated with an SS block that may have the best receiving signalquality. The wireless device may successfully detect a cell identifierthat may be associated with the cell and decode system information witha RACH configuration. The wireless device may use one PRACH preamble andselect one PRACH resource from RACH resources indicated by the systeminformation associated with the selected beam. A PRACH resource maycomprise at least one of: a PRACH index indicating a PRACH preamble, aPRACH format, a PRACH numerology, time and/or frequency radio resourceallocation, power setting of a PRACH transmission, and/or other radioresource parameters. For a contention-free RACH procedure, the PRACHpreamble and resource may be indicated in a DCI or other high layersignaling.

FIG. 16 shows an example of a random access procedure (e.g., via a RACH)that may include sending, by a base station, one or more SS blocks. Awireless device 1620 (e.g., a UE) may transmit one or more preambles toa base station 1621 (e.g., a gNB in NR). Each preamble transmission bythe wireless device may be associated with a separate random accessprocedure, such as shown in FIG. 16. The random access procedure maybegin at step 1601 with a base station 1621 (e.g., a gNB in NR) sendinga first SS block to a wireless device 1621 (e.g., a UE). Any of the SSblocks may comprise one or more of a PSS, SSS, tertiary synchronizationsignal (TSS), or PBCH signal. The first SS block in step 1601 may beassociated with a first PRACH configuration. At step 1602, the basestation 1621 may send to the wireless device 1620 a second SS block thatmay be associated with a second PRACH configuration. At step 1603, thebase station 1621 may send to the wireless device 1620 a third SS blockthat may be associated with a third PRACH configuration. At step 1604,the base station 1621 may send to the wireless device 1620 a fourth SSblock that may be associated with a fourth PRACH configuration. Anynumber of SS blocks may be sent in the same manner in addition to, orreplacing, steps 1603 and 1604. An SS burst may comprise any number ofSS blocks. For example, SS burst 1610 comprises the three SS blocks sentduring steps 1602-1604.

The wireless device 1620 may send to the base station 1621 a preamble,at step 1605, e.g., after or in response to receiving one or more SSblocks or SS bursts. The preamble may comprise a PRACH preamble, and maybe referred to as RA Msg 1. The PRACH preamble may be transmitted instep 1605 according to or based on a PRACH configuration that may bereceived in an SS block (e.g., one of the SS blocks from steps1601-1604) that may be determined to be the best SS block beam. Thewireless device 1620 may determine a best SS block beam from among SSblocks it may receive prior to sending the PRACH preamble. The basestation 1621 may send a random access response (RAR), which may bereferred to as RA Msg2, at step 1606, e.g., after or in response toreceiving the PRACH preamble. The RAR may be transmitted in step 1606via a DL beam that corresponds to the SS block beam associated with thePRACH configuration. The base station 1621 may determine the best SSblock beam from among SS blocks it previously sent prior to receivingthe PRACH preamble. The base station 1621 may receive the PRACH preambleaccording to or based on the PRACH configuration associated with thebest SS block beam.

The wireless device 1620 may send to the base station 1621 anRRCConnectionRequest and/or RRCConnectionResumeRequest message, whichmay be referred to as RA Msg3, at step 1607, e.g., after or in responseto receiving the RAR. The base station 1621 may send to the wirelessdevice 1620 an RRCConnectionSetup and/or RRCConnectionResume message,which may be referred to as RA Msg4, at step 1608, e.g., after or inresponse to receiving the RRCConnectionRequest and/orRRCConnectionResumeRequest message. The wireless device 1620 may send tothe base station 1621 an RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message, which may be referred to as RAMsg5, at step 1609, e.g., after or in response to receiving theRRCConnectionSetup and/or RRCConnectionResume. An RRC connection may beestablished between the wireless device 1620 and the base station 1621,and the random access procedure may end, e.g., after or in response toreceiving the RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message.

A best beam, including but not limited to a best SS block beam, may bedetermined based on a channel state information reference signal(CSI-RS). A wireless device may use a CSI-RS in a multi-beam system forestimating the beam quality of the links between the wireless device anda base station. For example, based on a measurement of a CSI-RS, awireless device may report CSI for downlink channel adaption. A CSIparameter may include a precoding matrix index (PMI), a channel qualityindex (CQI) value, and/or a rank indicator (RI). A wireless device mayreport a beam index based on a reference signal received power (RSRP)measurement on a CSI-RS. The wireless device may report the beam indexin a CSI resource indication (CRI) for downlink beam selection. A basestation may transmit a CSI-RS via a CSI-RS resource, such as via one ormore antenna ports, or via one or more time and/or frequency radioresources. A beam may be associated with a CSI-RS. A CSI-RS may comprisean indication of a beam direction. Each of a plurality of beams may beassociated with one of a plurality of CSI-RSs. A CSI-RS resource may beconfigured in a cell-specific way, e.g., via common RRC signaling.Additionally or alternatively, a CSI-RS resource may be configured in awireless device-specific way, e.g., via dedicated RRC signaling and/orlayer 1 and/or layer 2 (L1/L2) signaling. Multiple wireless devices inor served by a cell may measure a cell-specific CSI-RS resource. Adedicated subset of wireless devices in or served by a cell may measurea wireless device-specific CSI-RS resource. A base station may transmita CSI-RS resource periodically, using aperiodic transmission, or using amulti-shot or semi-persistent transmission. In a periodic transmission,a base station may transmit the configured CSI-RS resource using aconfigured periodicity in the time domain. In an aperiodic transmission,a base station may transmit the configured CSI-RS resource in adedicated time slot. In a multi-shot or semi-persistent transmission, abase station may transmit the configured CSI-RS resource in a configuredperiod. A base station may configure different CSI-RS resources indifferent terms for different purposes. Different terms may include,e.g., cell-specific, device-specific, periodic, aperiodic, multi-shot,or other terms. Different purposes may include, e.g., beam management,CQI reporting, or other purposes.

FIG. 17 shows an example of transmitting CSI-RSs periodically for abeam. A base station 1701 may transmit a beam in a predefined order inthe time domain, such as during time periods 1703. Beams used for aCSI-RS transmission, such as for CSI-RS 1704 in transmissions 1702Cand/or 1703E, may have a different beam width relative to a beam widthfor SS-blocks transmission, such as for SS blocks 1702A, 1702B, 1702D,and 1702F-1702H. Additionally or alternatively, a beam width of a beamused for a CSI-RS transmission may have the same value as a beam widthfor an SS block. Some or all of one or more CSI-RSs may be included inone or more beams. An SS block may occupy a number of OFDM symbols(e.g., 4), and a number of subcarriers (e.g., 240), carrying asynchronization sequence signal. The synchronization sequence signal mayidentify a cell.

FIG. 18 shows an example of a CSI-RS that may be mapped in time andfrequency domains. Each square shown in FIG. 18 may represent a resourceblock within a bandwidth of a cell. Each resource block may comprise anumber of subcarriers. A cell may have a bandwidth comprising a numberof resource blocks. A base station (e.g., a gNB in NR) may transmit oneor more RRC messages comprising CSI-RS parameters for one or moreCSI-RS. CSI-RS parameters for a CSI-RS may comprise, e.g., time and OFDMfrequency parameters, port numbers, CSI-RS index, and/or CSI-RS sequenceparameters. Time and frequency parameters may indicate, e.g.,periodicity, subframes, symbol numbers, OFDM subcarriers, and/or otherradio resource parameters. CSI-RS may be configured using commonparameters, e.g., when a plurality of wireless devices receive the sameCSI-RS signal. CSI-RS may be configured using wireless device dedicatedparameters, e.g., when a CSI-RS is configured for a specific wirelessdevice.

As shown in FIG. 18, three beams may be configured for a wirelessdevice, e.g., in a wireless device-specific configuration. Any number ofadditional beams (e.g., represented by the column of blank squares) orfewer beams may be included. Beam 1 may be allocated with CSI-RS 1 thatmay be transmitted in some subcarriers in a resource block (RB) of afirst symbol. Beam 2 may be allocated with CSI-RS 2 that may betransmitted in some subcarriers in a RB of a second symbol. Beam 3 maybe allocated with CSI-RS 3 that may be transmitted in some subcarriersin a RB of a third symbol. All subcarriers in a RB may not necessarilybe used for transmitting a particular CSI-RS (e.g., CSI-RS1) on anassociated beam (e.g., beam 1) for that CSI-RS. By using frequencydivision multiplexing (FDM), other subcarriers, not used for beam 1 forthe wireless device in the same RB, may be used for other CSI-RStransmissions associated with a different beam for other wirelessdevices. Additionally or alternatively, by using time domainmultiplexing (TDM), beams used for a wireless device may be configuredsuch that different beams (e.g., beam 1, beam 2, and beam 3) for thewireless device may be transmitted using some symbols different frombeams of other wireless devices.

Beam management may use a device-specific configured CSI-RS. In a beammanagement procedure, a wireless device may monitor a channel quality ofa beam pair link comprising a transmitting beam by a base station (e.g.,a gNB in NR) and a receiving beam by the wireless device (e.g., a UE).When multiple CSI-RSs associated with multiple beams are configured, awireless device may monitor multiple beam pair links between the basestation and the wireless device.

A wireless device may transmit one or more beam management reports to abase station. A beam management report may indicate one or more beampair quality parameters, comprising, e.g., one or more beamidentifications, RSRP, PMI, CQI, and/or RI, of a subset of configuredbeams.

A base station and/or a wireless device may perform a downlink L1/L2beam management procedure. One or more downlink L1/L2 beam managementprocedures may be performed within one or multiple transmission andreceiving points (TRPs). Procedure P-1 may be used to enable a wirelessdevice measurement on different TRP transmit (Tx) beams, e.g., tosupport a selection of TRP Tx beams and/or wireless device receive (Rx)beam(s). Beamforming at a TRP may include, e.g., an intra-TRP and/orinter-TRP Tx beam sweep from a set of different beams. Beamforming at awireless device, may include, e.g., a wireless device Rx beam sweep froma set of different beams. Procedure P-2 may be used to enable a wirelessdevice measurement on different TRP Tx beams, e.g., which may changeinter-TRP and/or intra-TRP Tx beam(s). Procedure P-2 may be performed,e.g., on a smaller set of beams for beam refinement than in procedureP-1. P-2 may be a particular example of P-1. P-3 may be used to enable awireless device measurement on the same TRP Tx beam, e.g., to change awireless device Rx beam if a wireless device uses beamforming.

Based on a wireless device's beam management report, a base station maytransmit, to the wireless device, a signal indicating that one or morebeam pair links are the one or more serving beams. The base station maytransmit PDCCH and/or PDSCH for the wireless device using the one ormore serving beams.

A wireless device (e.g., a UE) and/or a base station (e.g., a gNB) maytrigger a beam failure recovery mechanism. A wireless device may triggera beam failure recovery (BFR) request transmission, e.g., when a beamfailure event occurs. A beam failure event may include, e.g., adetermination that a quality of beam pair link(s) of an associatedcontrol channel is unsatisfactory. A determination of an unsatisfactoryquality of beam pair link(s) of an associated channel may be based onthe quality falling below a threshold and/or an expiration of a timer.

A wireless device may measure a quality of beam pair link(s) using oneor more reference signals (RS). One or more SS blocks, one or moreCSI-RS resources, and/or one or more demodulation reference signals(DM-RSs) of a PBCH may be used as a RS for measuring a quality of a beampair link. A quality of a beam pair link may be based on one or more ofan RSRP value, reference signal received quality (RSRQ) value, and/orCSI value measured on RS resources. A base station may indicate that anRS resource, e.g., that may be used for measuring a beam pair linkquality, is quasi-co-located (QCLed) with one or more DM-RSs of acontrol channel. The RS resource and the DM-RSs of the control channelmay be QCLed when the channel characteristics from a transmission via anRS to a wireless device, and the channel characteristics from atransmission via a control channel to the wireless device, are similaror the same under a configured criterion.

FIG. 19 shows an example of a beam failure event involving a single TRP.A single TRP such as at a base station 1901 may transmit, to a wirelessdevice 1902, a first beam 1903 and a second beam 1904. A beam failureevent may occur if, e.g., a serving beam, such as the second beam 1904,is blocked by a moving vehicle 1905 or other obstruction (e.g.,building, tree, land, or any object) and configured beams (e.g., thefirst beam 1903 and the second beam 1904), including the serving beam,are received from the single TRP. The wireless device 1902 may trigger amechanism to recover from beam failure when a beam failure occurs.

FIG. 20 shows an example of a beam failure event involving multipleTRPs. Multiple TRPs, such as at a first base station 2001 and at asecond base station 2006, may transmit, to a wireless device 2002, afirst beam 2003 (e.g., from the first base station 2001) and a secondbeam 2004 (e.g., from the second base station 2006). A beam failureevent may occur when, e.g., a serving beam, such as the second beam2004, is blocked by a moving vehicle 2005 or other obstruction (e.g.,building, tree, land, or any object) and configured beams (e.g., thefirst beam 2003 and the second beam 2004) are received from multipleTRPs. The wireless device 2002 may trigger a mechanism to recover frombeam failure when a beam failure occurs.

A wireless device may monitor a PDCCH, such as a New Radio PDCCH(NR-PDCCH), on M beam pair links simultaneously, where M≥1 and themaximum value of M may depend at least on the wireless devicecapability. Such monitoring may increase robustness against beam pairlink blocking. A base station may transmit, and the wireless device mayreceive, one or more messages configured to cause the wireless device tomonitor NR-PDCCH on different beam pair link(s) and/or in differentNR-PDCCH OFDM symbols.

A base station may transmit higher layer signaling, and/or a MAC controlelement (MAC CE), that may comprise parameters related to a wirelessdevice Rx beam setting for monitoring NR-PDCCH on multiple beam pairlinks. A base station may transmit one or more indications of a spatialQCL assumption between a first DL RS antenna port(s) and a second DL RSantenna port(s). The first DL RS antenna port(s) may be for one or moreof a cell-specific CSI-RS, device-specific CSI-RS, SS block, PBCH withDM-RSs of PBCH, and/or PBCH without DM-RSs of PBCH. The second DL RSantenna port(s) may be for demodulation of a DL control channel.Signaling for a beam indication for a NR-PDCCH (e.g., configuration tomonitor NR-PDCCH) may be via MAC CE signaling, RRC signaling, DCIsignaling, or specification-transparent and/or an implicit method, andany combination thereof.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. A base station may transmit DCI (e.g.,downlink grants) comprising information indicating the RS antennaport(s). The information may indicate the RS antenna port(s) which maybe QCLed with DM-RS antenna port(s). A different set of DM-RS antennaport(s) for the DL data channel may be indicated as a QCL with adifferent set of RS antenna port(s).

If a base station transmits a signal indicating a spatial QCL parametersbetween CSI-RS and DM-RS for PDCCH, a wireless device may use CSI-RSsQCLed with DM-RS for a PDCCH to monitor beam pair link quality. If abeam failure event occurs, the wireless device may transmit a beamfailure recovery request, such as by a determined configuration.

If a wireless device transmits a beam failure recovery request, e.g.,via an uplink physical channel or signal, a base station may detect thatthere is a beam failure event, for the wireless device, by monitoringthe uplink physical channel or signal. The base station may initiate abeam recovery mechanism to recover the beam pair link for transmittingPDCCH between the base station and the wireless device. The base stationmay transmit one or more control signals, to the wireless device, e.g.,after or in response to receiving the beam failure recovery request. Abeam recovery mechanism may be, e.g., an L1 scheme, or a higher layerscheme.

A base station may transmit one or more messages comprising, e.g.,configuration parameters of an uplink physical channel and/or a signalfor transmitting a beam failure recovery request. The uplink physicalchannel and/or signal may be based on at least one of the following: anon-contention based PRACH (e.g., a beam failure recovery PRACH orBFR-PRACH), which may use a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., beam failure recovery PUCCH orBFR-PUCCH); and/or a contention-based PRACH resource. Combinations ofthese candidate signal and/or channels may be configured by a basestation.

If a beam failure occurs, a beam failure recovery procedure may beperformed. A wireless device may send, to a base station, a beam failurerecovery (BFR) request or one or more messages associated with a BFRrequest. The base station may send one or more transmissions associatedwith a BFR request. The wireless device may have one or more BFRrequests for a transmission, overlapping in time with a transmission ofone or more other messages. An amount of transmission power required bythe wireless device for such overlapping transmissions may exceed amaximum allowable transmission power. Restrictions on total transmissionpower may be determined to set a threshold maximum allowabletransmission power that can be utilized by the wireless device or basestation at a given point in time. For example, a regulatory group, suchas Underwriters Laboratories, or a group such as 3GPPP, may specifyrestrictions associated with one or more regulatory certifications,standards, recommendations, etc. The threshold maximum allowable powermay apply to a total transmission power for a limited set of frequenciesor antennas, or the threshold may apply to a plurality of frequencies orantennas. It may be advantageous to perform methods to control powertransmission such that multiple requests do not exceed the threshold.The methods may reduce the total transmission power for one or moreoverlapping transmissions by reducing power for one or more overlappingtransmission, e.g., according to a prioritization scheme, such that thetotal transmission power of the overlapping transmissions does notexceed the threshold maximum allowable transmission power. This may havethe advantage of reducing power to one or more transmissions that areless important (e.g., one or more messages with an indicated lowerpriority), so that more important transmissions (e.g., one or more BFRrequests having an indicated higher priority) have less or no reductionin transmission power.

A wireless device may receive, and a base station may transmit, one ormore radio resource control messages. The one or more radio resourcecontrol message may comprise first configuration parameters of at leastone cell, and second configuration parameters of a random access (RA)procedure for a beam failure recovery (BFR). The at least one cell maybe grouped into multiple cell groups. The wireless device may initiatethe RA procedure for a BFR, e.g., after at least one beam failure on afirst cell of the at least one cell. The first cell may be a primarycell of a first cell group of the multiple cell groups.

The wireless device may detect the at least one beam failure, e.g.,based on determining that a measured mean link quality is below athreshold. The measured beam link quality may be based on one or moreof: a reference signal received power, or a reference signal receivedquality. The wireless device may determine, e.g., based on the secondconfiguration parameters, a first transmission power of a firstpreamble. The wireless device may select the first preamble from aplurality of preambles, e.g., based on initiating the RA procedure forthe BFR. The wireless device may determine that a first configuredtransmission, of the first preamble via the first cell, overlaps in timewith a second configured transmission of a second preamble. The wirelessdevice may adjust a second transmission power of the second preamble sothat a total power, comprising the first transmission power and a secondtransmission power of the second configured transmission, does notexceed a total allowable power value. The wireless device may transmit,using the adjusted second transmission power, the second preamble. Thetransmitting the second preamble may be via a second cell that is asecondary cell of a second cell group of the multiple cell groups. Thewireless device may initiate a second RA procedure based on at least oneof: an initial access procedure, a handover command, or a physicaldownlink control channel order. The wireless device may transmit, usingthe first transmission power, the first preamble. The base station mayreceive the second preamble, and the base station may receive the firstpreamble.

Additionally or alternatively, the wireless device may determine that afirst configured transmission, of a preamble (e.g., the first preamble)via the first cell, overlaps in time with a second configuredtransmission of a second signal. The wireless device may determine thata total power, comprising a first transmission power of the firstconfigured transmission and a second transmission power of the secondconfigured transmission, exceeds a total allowable power value. Thewireless device may drop the second signal, e.g., based on thedetermination that the total power exceeds the allowable power value.The wireless device may transmit, using the first transmission power,the preamble.

Additionally or alternatively, the wireless device may initiate ascheduling request (SR) procedure for the BFR. The wireless device maydetermine a first transmission power of a configured transmission viathe first cell of a first signal associated with the SR procedure. Thewireless device may determine that the configured transmission of thefirst signal overlaps in time with a configured transmission of a secondsignal. The second signal may be for an uplink transmission via one ormore of: a physical uplink control channel, or a physical uplink sharedchannel. The second signal may be a sounding reference signal. The firstsignal may be for an uplink transmission via a first physical randomaccess channel (PRACH), and the second signal may be for an uplinktransmission via a second PRACH. The wireless device may determine thata total power, comprising the first transmission power and a secondtransmission power of the configured transmission of the second signal,exceeds a total allowable power value. Based on the determination thatthe total power exceeds a total allowable power value, the wirelessdevice may: adjust the second transmission power so that the total powerdoes not exceed the total allowable power value, and/or drop the secondsignal. The wireless device may transmit, using the first transmissionpower, the first signal. The wireless device may transmit, using theadjusted second transmission power, the second signal.

A wireless device may determine an expected transmission power for aPUSCH (Physical Uplink Shared Channel) transmission according to one ormore system configurations. For example, an expected PUSCH transmissionmay be performed for a single carrier, for carrier aggregation, for dualconnectivity (DC), or for multiple PUCCH-Secondary Cells.

A single carrier may be used if, e.g., a wireless device transmits aPUSCH transmission without a simultaneous PUCCH transmission for aserving cell c. For a single carrier, the wireless device transmit powerP_(PUSCH,c)(i) for the PUSCH transmission in subframe i for the servingcell c may be given by the equation:

${P_{{PUSCH},c}(i)} = {\min \begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{10\; {\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCH},c}(j)} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}{\quad{\lbrack{dBm}\rbrack.}}}$

If a wireless device transmits a PUSCH transmission simultaneous with aPUCCH transmission associated with the serving cell c, the wirelessdevice transmit power P_(PUSCH,c)(i) for the PUSCH transmission insubframe i for the serving cell c may be given by the equation:

${P_{{PUSCH},c}(i)} = {\min \begin{Bmatrix}{{10\; {\log_{10}\left( {{{\hat{P}}_{{CMAX},c}(i)} - {{\hat{P}}_{PUCCH}(i)}} \right)}},} \\{{10\; {\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCH},c}(j)} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}{\quad\lbrack{dBm}\rbrack}}$

wherein:

-   -   P_(CMAX,c)(i) may be a configured wireless device transmission        power in subframe i for serving cell c,    -   {circumflex over (P)}_(CMAX,c)(i) may be a linear value of        P_(CMAX,c)(i),    -   {circumflex over (P)}_(PUCCH)(i) may be a linear value of        P_(PUCCH)(i),    -   M_(PUSCH,c)(i) may be a bandwidth of the PUSCH resource        assignment expressed in number of resource blocks valid for        subframe i and serving cell c, and/or    -   PL_(c) may be a downlink pathloss estimate for the wireless        device serving cell c in dB.

It may be that PL_(c)=referenceSignalPower, which may be a higher-layerfiltered reference signal power (RSRP). The referenceSignalPower may beprovided by higher layers, RSRP may be determined for the referenceserving cell, and a higher-layer filter configuration may be used forthe reference serving cell.

Carrier aggregation may be used if, e.g., a base station transmits, to awireless device, one or more messages comprising configurationparameters associated with one or multiple serving cells.

If the total transmit power of the wireless device would exceed{circumflex over (P)}_(CMAX)(i), a wireless device may scaleP_(PUSCH,c)(i) for the serving cell c in subframe i such that thecondition

${\sum\limits_{c}\; {{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{PUCCH}(i)}} \right)$

may be satisfied, wherein:

-   -   {circumflex over (P)}_(PUCCH)(i) may be a linear value of        P_(PUCCH)(i),    -   {circumflex over (P)}_(PUSCH,c)(i) may be a linear value of        P_(PUSCH,c)(i),    -   {circumflex over (P)}_(CMAX)(i) may be a linear value of the        wireless device total configured maximum output power P_(CMAX)        in subframe i, and/or    -   w(i) may be a scaling factor of {circumflex over        (P)}_(PUSCH,c)(i) for serving cell c, where 0≤w(i)≤1.

If there is no PUCCH transmission in subframe i, power may be adjustedsuch that {circumflex over (P)}_(PUCCH)(i)=0.

If a wireless device has a PUSCH transmission with uplink controlinformation (UCI) on serving cell j, the wireless device has a PUSCHtransmission without UCI in any of the remaining serving cells, and thetotal transmit power of the wireless device would exceed {circumflexover (P)}_(CMAX)(i), the wireless device may scale {circumflex over(P)}_(CMAX)(i) for the serving cells without UCI in subframe i such thatthe condition

${\sum\limits_{c \neq j}\; {{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right)$

may be satisfied, wherein:

{circumflex over (P)}_(PUSCH,j)(i) may be a PUSCH transmit power for thecell with UCI, and/or

w(i) may be a scaling factor of P_(PUSCH,c)(i) for serving cell cwithout UCI.

If the above occurs, it may be that no power scaling may be performedfor {circumflex over (P)}_(PUSCH,j)(i) unless

${\sum\limits_{c \neq j}\; {{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} = 0$

and the total transmit power of the wireless device would exceed{circumflex over (P)}_(CMAX)(i).

A wireless device may transmit a PUCCH transmission and a PUSCHtransmission in a substantially concurrent fashion, e.g., with a PUCCHtransmission with UCI on serving cell j and a PUSCH transmission withoutUCI in any of the remaining serving cells. If this occurs, and the totaltransmission power of the wireless device would exceed {circumflex over(P)}_(CMAX)(i), the wireless device may obtain {circumflex over(P)}_(PUSCH,c)(i) according to:

P̂_(PUSCH, j)(i) = min (P̂_(PUSCH, j)(i), (P̂_(CMAX)(i) − P̂_(PUCCH)(i)))and/or${\sum\limits_{c \neq j}\; {{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq {\left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{PUCCH}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right).}$

If a wireless device is configured without a Secondary Cell Group (SCG)or a PUCCH Secondary Cell (PUCCH-SCell), the wireless device isconfigured with multiple TAGs, and the PUCCH/PUSCH transmission of thewireless device on subframe i for a given serving cell in a TAG overlapssome portion of the first symbol of the PUSCH transmission on subframei+1 for a different serving cell in another TAG, the wireless device mayadjust its total transmission power so as not to exceed P_(CMAX) on anyoverlapped portion.

If the wireless device is configured with multiple TAGs, and the PUSCHtransmission of the wireless device on subframe i for a given servingcell in a TAG overlaps some portion of the first symbol of the PUCCHtransmission on subframe i+1 for a different serving cell in anotherTAG, the wireless device may adjust its total transmission power so asnot to exceed P_(CMAX) on any overlapped portion.

If the wireless device is configured with multiple TAGs, the soundingreference signal (SRS) transmission of the wireless device in a symbolon subframe i for a given serving cell in a TAG overlaps with thePUCCH/PUSCH transmission on subframe i or subframe i+1 for a differentserving cell in a TAG (which may be the same TAG or a different TAG),and the total transmission power for the wireless device exceedsP_(CMAX), the wireless device may drop SRS transmissions.

If the wireless device is configured with multiple TAGs and more thantwo serving cells, the SRS transmission of the wireless device in asymbol on subframe i for a given serving cell overlaps with:

-   -   the SRS transmission on subframe i for a serving cell(s) other        than the given serving cell, and    -   a PUSCH transmission or PUCCH transmission on subframe i or        subframe i+1 for a serving cell(s),

and the total transmission power exceeds P_(CMAX) on any overlappedportion of the symbol, the wireless device may drop SRS transmissions.

If the wireless device is configured with multiple TAGs, the wirelessdevice may, after being requested (e.g., by higher layers) to transmitPRACH in a secondary serving cell belonging to a first TAG in parallelwith an SRS transmission in a symbol on a subframe of a differentserving cell belonging to a different TAG, drop SRS transmissions if thetotal transmission power exceeds P_(CMAX) on any overlapped portion ofthe symbol.

If the wireless device is configured with multiple TAGs, the wirelessdevice may, when requested by higher layers, to transmit on a PRACH in asecondary serving cell in parallel with a PUSCH transmission or a PUCCHtransmission in a different serving cell belonging to a different TAG,adjust the transmission power of the PUSCH transmission or the PUCCHtransmission so that the total transmission power does not exceedP_(CMAX) on the overlapped portion.

A wireless device may trigger a BFR request transmission on an uplinkchannel. The uplink channel may be a PRACH, a frequency resourcedifferent from a normal PRACH, or a PUCCH.

A wireless device may transmit a BFR request simultaneously with otheruplink transmissions, e.g., one or more of: a normal PRACH transmission,a scheduling request (SR) transmission, a PUCCH transmission, a PUSCHtransmission, or an SRS transmission.

FIG. 21 shows an example of a BFR-PRACH transmission in conjunction witha regulated transmission. This example may apply, e.g., for CA. A basestation 2101 may configure a wireless device 2102 with a primary celland a secondary cell on a first carrier frequency 2103 and a secondcarrier frequency 2104, respectively. The base station 2101 mayconfigure the wireless device 2102 with a normal PRACH transmission onthe first carrier frequency 2103. The base station 2101 may configurethe wireless device 2102 with a BFR PRACH transmission on the secondcarrier frequency 2104. The base station 2101 may transmit data to awireless device 2102, e.g., using multiple beams on the second carrierfrequency 2104 and using a single beam on the first carrier frequency2103.

The base station 2101 may configure the cell on the second carrierfrequency 2104 as a primary cell and the base station 2101 may configurethe cell on the first carrier frequency 2103 as a secondary cell.

The wireless device 2102 may trigger a normal PRACH transmission on thefirst carrier frequency 2103 based on some event. For example, if thewireless device is in an RRC_CONNECTED state, but the wireless device isnot UL-SYNCed to the cell on the first carrier frequency 2103, it may beadvantageous for the wireless device 2102 to send new UL data. Thewireless device 2102 may trigger a BFR request transmission on aBFR-PRACH on the second carrier frequency 2104 based on some event,e.g., when a downlink beam failure occurs. The wireless device 2102 maytransmit a normal PRACH on the first carrier frequency 2103 and thewireless device 2102 transmit a BFR PRACH on the second carrierfrequency 2104.

The wireless device 2102 may transmit a PUCCH transmission, a PUSCHtransmission, or an SRS transmission on the first carrier frequency2103, and the wireless device 2102 may do so substantially concurrentlywith triggering a BFR request transmission on a BFR-PRACH on the secondcarrier frequency 2104. The wireless device 2102, if configured withmultiple serving cells, may determine, using a criterion, transmit powerfor a BFR PRACH transmission in parallel with one or more of: a PRACHtransmission, a PUCCH transmission, a PUSCH transmission, or an SRStransmission.

FIG. 22 shows an example of a BFR request transmission in a multiple-TRPsystem. In a multiple-TRP system, a base station may configure awireless device 2202 with a plurality of beams, e.g., a first beam 2203from a TRP 2201, and a second beam 2204 from a TRP 2206. The TRPs (e.g.,TRP 2201 and TRP 2206) may belong to one base station and/or differentbase stations.

The wireless device 2202 may be equipped with two antenna panels. Onepanel may be used for transmitting to and receiving via the first beam2203 from the TRP 2201, and another panel may be used for transmittingto and receiving via the second beam 2204 from the TRP 2206.

The base station may configure the wireless device 2202 with normalPRACH transmission on a beam pair link (BPL) via the first beam 2203,and the base station may configure the wireless device 2202 with a BFRPRACH transmission on a BPL via the second beam 2204.

The wireless device 2202 may trigger a normal PRACH transmission on theBPL via the first beam 2203 based on an event. For example, when thewireless device 2202 is in an RRC_CONNECTED state, but not UL-SYNCed tothe cell associated with the TRP 2201, it may be advantageous for thewireless device 2202 to send new UL data. The wireless device 2202 maytrigger a BFR request transmission via the TRP 2206 based on a beamfailure event. For example, the wireless device 2202 may transmit anormal PRACH on the BPL via the first beam 2203 and the wireless device2202 may transmit a BFR PRACH on the BPL via the second beam 2204.

The wireless device 2202 may transmit a PUCCCH transmission, a PUSCHtransmission, and/or an SRS transmission on the BPL via the first beam2203, and simultaneously, the wireless device 2202 may transmit a BFRPRACH on the BPL via the second beam 2204. If beam failure events occuron both BPLs, the wireless device 2202 may trigger BFR requesttransmissions on both BPLs.

If the wireless device 2202 is configured with multiple TRPs, thewireless device 2202 may determine, based on a criterion, a transmissionpower for a BFR-PRACH transmission in parallel with one or more of: aBFR-PRACH transmission, a normal PRACH transmission, a PUCCHtransmission, a PUSCH transmission, or an SRS transmission.

FIG. 23 shows an example of processes for a wireless device for beamfailure recovery requests. A base station may transmit one or moremessages comprising configuration parameters indicating one or morePRACH resources for a wireless device. The base station may transmit theone or more messages via RRC messaging. The configuration parameters mayindicate one or more serving cells. The configuration parameters mayindicate one or more PRACH resources for BFR requests. The configurationparameters may comprise one or more preambles and/or RSs. RS resourcesmay comprise one or more of: CSI-RSs, SS blocks, or DMRSs of a PBCH. Theconfiguration parameters may comprise one or more TRPs. Theconfiguration parameters may comprise one or more first preambles and/orPRACHs associated with first RSs, one or more second preambles and/orPRACHs associated with second RSs, and/or one or more third (or othernumber) preambles and/or PRACHs associated with third (or other number)RSs. The configuration parameters may indicate one or more prioritiesfor a BFR-PRACH. For example, BFR-PRACH transmission may be prioritizedabove or below PUCCH transmissions, PUSCH transmissions, PRACHtransmissions, and/or other transmission types.

At step 2301, a wireless device may receive, from the base station, theconfiguration parameters. The configuration parameters may be used toconfigure the wireless device with a transmit beam. The configurationparameters may configure the wireless device with configured and/oractivated transmit beams. The base station may use the serving beam totransmit, and the wireless device may use the serving beam to receive,PDCCH signals and associated PDSCH signals for the wireless device.

The wireless device may monitor reference signals for a potential beamfailure at step 2302, e.g., after receiving configuration parameters.The wireless device may monitor a first set of RSs based on a firstthreshold. The first set of RSs may correspond to CSI-RSs of a servingbeam. The first threshold may be determined, e.g., based on measurementsfrom one or more previous beam failure events. The first threshold maybe set to a value at or near an average of previous beam failure events,or to a value above some or all previous beam failure events. Thewireless device may monitor periodically, for a duration of time (e.g.,until an expiration of a timer), or until the first RSs fall below thefirst threshold.

At step 2303, the wireless device may detect a beam failure event. Adetection of a beam failure event may comprise the wireless devicedetermining that a channel quality of the first RSs fall below the firstthreshold. Additionally or alternatively, a detection of a beam failureevent may comprise one or more measurements of a channel quality fallingbelow the first threshold. The beam failure event may be on a servingbeam. If a beam failure event occurs on the serving beam, the wirelessdevice may monitor configured and/or activated beams.

At step 2304, the wireless device may determine a transmission power ofan uplink channel or signal using a power control calculation. Thetransmission power may be configured for the entire wireless device,some physical part of the wireless device (e.g., a subset of one or moreantennas of the wireless device), and/or some virtual part of thewireless device (e.g., one or more serving cells). The wireless devicemay determine the transmission power employing an open-loop powercalculation and/or a closed-loop power calculation.

The wireless device may measure a pathloss value based on one or moredownlink reference signals. The wireless device may employ the pathlossvalue to determine an open-loop power value. The wireless device mayreceive one or more power control commands to determine a closed-looppower offset value for transmission in a transmission time interval(TTI).

At step 2305, the wireless device may determine if a BFR-PRACHtransmission is prioritized over a PUCCH transmission. For example, aconfiguration parameter received from the base station may indicate thata BFR-PRACH transmission is prioritized over a PUCCH transmission. TheBFR-PRACH transmission may be predefined or preconfigured to beprioritized over a PUCCH transmission. If a BFR-PRACH transmission isdetermined to be prioritized over a PUCCH transmission, the method maycontinue at step 2306. If a BFR-PRACH transmission is determined to notbe prioritized over a PUCCH transmission, the method may continue atstep 2307.

At step 2306, the wireless device may adjust transmission power based ondetermining that a BFR-PRACH transmission is prioritized over a PUCCHtransmission. If a wireless device triggers a BFR request transmissionon a BFR-PRACH on a serving cell in parallel with a PUSCH transmissionor a PUCCH transmission on different serving cells, the wireless devicemay adjust the transmission power of the PUCCH transmission or the PUSCHtransmission so that the total transmission power of the wireless devicedoes not exceed a configured or predefined value (e.g., P_(CMAX)).

If a wireless device triggers, in subframe i, a PUSCH transmission and aBFR-PRACH transmission on a serving cell, the wireless device maydetermine if the total transmission power of the wireless device wouldexceed {circumflex over (P)}_(MAX)(i). If the total transmission powerof the wireless device would exceed {circumflex over (P)}_(CMAX)(i), thewireless device may scale {circumflex over (P)}_(PUSCH,c)(i) for theserving cell c in subframe i such that the condition

${\sum\limits_{c}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{{BFR}\text{-}{PRACH}}(i)} - {{\hat{P}}_{PUCCH}(i)}} \right)$

may be satisfied, wherein:

-   -   {circumflex over (P)}_(PUCCH)(i) may be a linear value of        {circumflex over (P)}_(PUCCH)(i),    -   {circumflex over (P)}_(BFR-PRACH)(i) may be a linear value of        P_(BFR-PRACH)(i), which may be a transmission power for a BFR        request on a BFR-PRACH,    -   {circumflex over (P)}_(PUSCH,c)(i) may be a linear value of        P_(PUSCH,c)(i),    -   {circumflex over (P)}_(CMAX)(i) may be a linear value of the        wireless device total configured maximum output power P_(CMAX)        in subframe i, and    -   w(i) may be a scaling factor of {circumflex over        (P)}_(PUSCH,c)(i) for serving cell c, where 0≤w(i)≤1.

No power scaling may be performed for {circumflex over (P)}_(PUCCH)(i)unless

${\sum\limits_{c}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} = 0$

and the total transmit power of the wireless device would exceed{circumflex over (P)}_(CMAX)(i). If there is no PUCCH transmission insubframe i, power may be adjusted such that {circumflex over(P)}_(PUCCH)(i)=0. If there is no BFR-PRACH transmission in subframe i,power may be adjusted such that {circumflex over (P)}_(BFR-PRACH)(i)=0.

A wireless device may trigger, in subframe i, a BFR-PRACH transmissionon a serving cell, a PUSCH transmission with UCI on serving cell j, anda PUSCH without UCI transmission in one or more of the remaining servingcells. If this occurs, and the total transmission power of the wirelessdevice would exceed {circumflex over (P)}_(CMAX)(i), the wireless devicemay scale {circumflex over (P)}_(PUSCH,c)(i) for the serving cellswithout UCI in subframe i such that the condition

${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{{BFR}\text{-}{PRACH}}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right)$

may be satisfied, wherein:

-   -   {circumflex over (P)}_(PUSCH,j)(i) is a PUSCH transmit power for        the cell with UCI, and    -   w(i) is a scaling factor of {circumflex over (P)}_(PUSCH,c)(i)        for serving cell c without UCI.

No power scaling may be performed for {circumflex over (P)}_(PUSCH,j)(i)unless

${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} = 0$

and the total transmission power of the wireless device still wouldexceed {circumflex over (P)}_(CMAX)(i). If there is no BFR-PRACHtransmission in subframe i, power may be adjusted such that {circumflexover (P)}_(BFR-PRACH)(i)=0.

A wireless device may trigger, in subframe i, a BFR-PRACH transmissionon a serving cell, a substantially concurrent PUCCH transmission andPUSCH transmission with UCI on serving cell j, and a PUSCH transmissionwithout UCI in one or more of the remaining serving cells. If thisoccurs, and the total transmission power of the wireless device wouldexceed {circumflex over (P)}_(CMAX)(i), the wireless device may obtain{circumflex over (P)}_(PUSCH,c)(i) according to

P̂_(PUSCH, j)(i) = min (P̂_(PUSCH, j)(i), (P̂_(CMAX)(i) − P̂_(BFR-PRACH)(i) − P̂_(PUCCH)(i)))and${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq {\left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{{BFR}\text{-}{PRACH}}(i)} - {{\hat{P}}_{PUCCH}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right).}$

A wireless device configured with a BFR-PRACH on a serving cell, whichis transmitted in parallel with an SRS transmission in different servingcells, may drop the SRS transmission if the total power for paralleltransmission of the BFR-PRACH and the SRS transmission would exceed aconfigured or predefined value (e.g., P_(CMAX)).

The power adjustment of step 2306 may be performed if a base stationconfigures a wireless device with other uplink channels to transmit aBFR request (e.g., a scheduling request PUCCH (SR/PUCCH)). For example,a base station may configure a wireless device with an SR/PUCCH for aBFR request transmission (e.g., BFR-PUCCH). The wireless device maydetermine an uplink transmission power as described above regarding step2306 by substituting BFR-PUCCH for BFR-PRACH.

Transmissions may resume using the adjusted values in step 2314, e.g.,after adjusting the transmission power according to the priority such asdescribed above.

At step 2307, the wireless device may determine if a BFR-PRACHtransmission is prioritized over a PUSCH transmission with UCI. Forexample, a configuration parameter received from the base station mayindicate that a BFR-PRACH transmission is prioritized over a PUSCHtransmission with UCI. The BFR-PRACH transmission may be predefined orpreconfigured to be prioritized over a PUSCH transmission with UCI. If aBFR-PRACH transmission is determined to be prioritized over a PUSCHtransmission with UCI, the method may continue at step 2308. If aBFR-PRACH transmission is determined to not be prioritized over a PUSCHtransmission with UCI, the method may continue at step 2309.

At step 2308, the wireless device may adjust transmission power based ondetermining that a BFR-PRACH transmission is prioritized over a PUSCHtransmission with UCI. If a wireless device triggers a BFR requesttransmission on a BFR-PRACH on a serving cell in parallel with a PUSCHtransmission or a PUCCH transmission on different serving cells, thewireless device may adjust the transmission power of the BFR-PRACH onthe serving cell and the PUSCH on other serving cells so that the totaltransmission power of the wireless device does not exceed a configuredor predefined value (e.g., P_(CMAX)).

A wireless device may trigger, in subframe i, a BFR-PRACH transmissionon a serving cell and a PUSCH with UCI transmission. If this occurs, andthe total transmit power of a wireless device would exceed {circumflexover (P)}_(CMAX)(i), the wireless device may scale {circumflex over(P)}_(PUSCH,c)(i) for the serving cell c in subframe i such that thecondition

${\sum\limits_{c}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{PUCCH}(i)} - {{\hat{P}}_{{BFR}\text{-}{PRACH}}(i)}} \right)$

may be satisfied, wherein:

-   -   {circumflex over (P)}_(PUCCH)(i) may be a linear value of        P_(PUCCH)(i),    -   P_(BFR-PRACH)(i) may be a linear value of P_(BFR-PRACH)(i),        which may be a transmission power for a BFR request on        BFR-PRACH,    -   {circumflex over (P)}_(PUSCH,c)(i) may be a linear value of        P_(PUSCH,c)(i),    -   {circumflex over (P)}_(CMAX)(i) may be a linear value of the        wireless device total configured maximum output power P_(CMAX)        in subframe i, and    -   w(i) may be a scaling factor of P_(PUSCH,c)(i) for serving cell        c, where 0≤w(i)≤1.

No power scaling may be performed for {circumflex over(P)}_(BFR-PRACH)(i) unless

${\sum\limits_{c}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} = 0$

and the total transmit power of the wireless device would exceed{circumflex over (P)}_(CMAX)(i). If there is no PUCCH transmission insubframe i, power may be adjusted such that {circumflex over(P)}_(PUCCH)(i)=0. If there is no BFR-PRACH transmission in subframe i,power may be adjusted such that {circumflex over (P)}_(BFR-PRACH)(i)=0.

A wireless device may trigger, in subframe i, a BFR-PRACH transmissionon a serving cell, a PUSCH transmission with UCI on serving cell j, anda PUSCH without UCI in one or more of the remaining serving cells. Ifthis occurs, and the total transmit power of the wireless device wouldexceed {circumflex over (P)}_(CMAX)(i), the wireless device may scale{circumflex over (P)}_(PUSCH,c)(i) for the serving cells without UCI insubframe i such that the condition

${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{{BFR}\text{-}{PRACH}}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right)$

may be satisfied, wherein:

-   -   {circumflex over (P)}_(PUSCH,j)(i) may be a PUSCH transmit power        for the cell with UCI, and    -   w(i) may be a scaling factor of {circumflex over        (P)}_(PUSCH,c)(i) for serving cell c without UCI.

If the above occurs, no power scaling may be performed for {circumflexover (P)}_(BFR-PRACH)(i) and {circumflex over (P)}_(PUSCH,j)(i) unless

${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} = 0$

and the total transmit power of the wireless device still would exceed{circumflex over (P)}_(CMAX)(i). If there is no BFR-PRACH transmissionin subframe i, power may be adjusted such that {circumflex over(P)}_(BFR-PRACH)(i)=0.

A wireless device may trigger, in subframe i, a BFR-PRACH transmissionon a serving cell, a simultaneous PUCCH transmission and PUSCHtransmission with UCI on serving cell j, and a PUSCH transmissionwithout UCI in one or more of the remaining serving cells. If thisoccurs, and the total transmission power of the wireless device wouldexceed {circumflex over (P)}_(CMAX)(i), the wireless device may obtain{circumflex over (P)}_(PUSCH,c)(i) according to

P̂_(PUSCH, j)(i) = min (P̂_(PUSCH, j)(i), (P̂_(CMAX)(i) − P̂_(BFR-PRACH)(i) − P̂_(PUCCH)(i)))and${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq {\left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{{BFR}\text{-}{PRACH}}(i)} - {{\hat{P}}_{PUCCH}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right).}$

A wireless device configured with a BFR-PRACH transmission on a servingcell, which is transmitted in parallel with an SRS transmission indifferent serving cells, may drop the SRS transmission if the totalpower for parallel transmission of the BFR-PRACH transmission and theSRS transmission would exceed a configured or predefined value (e.g.,P_(CMAX)).

The power adjustment of step 2308 may be performed if a base stationconfigures a wireless device with other uplink channels to transmit aBFR request (e.g., an SR/PUCCH). For example, a base station mayconfigure a wireless device with an SR/PUCCH for a BFR requesttransmission (e.g., BFR-PUCCH). The wireless device may determine uplinktransmission power as described above regarding step 2308 bysubstituting BFR-PUCCH for BFR-PRACH.

Transmissions may resume using the adjusted values in step 2314, e.g.,after adjusting the transmission power according to the priority such asdescribed above.

At step 2309, the wireless device may determine if a BFR-PRACHtransmission is prioritized over a PUSCH transmission without UCI. Forexample, a configuration parameter received from the base station mayindicate that a BFR-PRACH transmission is prioritized over a PUSCHtransmission without UCI. The BFR-PRACH transmission may be predefinedor preconfigured to be prioritized over a PUSCH transmission withoutUCI. If a BFR-PRACH transmission is determined to be prioritized over aPUSCH transmission without UCI, the method may continue at step 2310. Ifa BFR-PRACH transmission is determined to not be prioritized over aPUSCH transmission without UCI, the method may continue at step 2311.

At step 2310, the wireless device may adjust transmission power based ondetermining that a BFR-PRACH transmission is prioritized over a PUSCHtransmission without UCI. If a wireless device triggers a BFR requesttransmission on a BFR-PRACH on a serving cell in parallel with a PUSCHtransmission or a PUCCH transmission on different serving cells, thewireless device may adjust the transmission power of the BFR-PRACH onthe serving cell and the PUSCH on other serving cells so that the totaltransmission power of the wireless device does not exceed a configuredor predefined value (e.g., P_(CMAX)).

At step 2310, the wireless device may adjust transmission power based ondetermining that a BFR-PRACH transmission is prioritized over a PUSCHtransmission without UCI. If a wireless device triggers a BFR requesttransmission on a BFR-PRACH on a serving cell in parallel with a PUSCHtransmission or a PUCCH transmission on different serving cells, thewireless device may adjust the transmission power of the BFR-PRACH onthe serving cell and the PUSCH without UCI on other serving cells sothat the total transmission power of the wireless device does not exceeda configured or predefined value (e.g., P_(CMAX)).

A wireless device may trigger, in subframe i, a BFR-PRACH transmissionon a serving cell and a PUSCH with UCI transmission. If this occurs, andthe total transmit power of a wireless device would exceed {circumflexover (P)}_(CMAX)(i), the wireless device may scale {circumflex over(P)}_(PUSCH,c)(i) for the serving cell c in subframe i such that thecondition

${\sum\limits_{c}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{PUCCH}(i)} - {{\hat{P}}_{{BFR}\text{-}{PRACH}}(i)}} \right)$

may be satisfied. No power scaling may be performed for {circumflex over(P)}_(BFR-PRACH)(i) unless

${\sum\limits_{c}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} = 0$

and the total transmit power of the wireless device would exceed{circumflex over (P)}_(CMAX)(i). If there is no PUCCH transmission insubframe i, power may be adjusted such that {circumflex over(P)}_(PUCCH)(i)=0. If there is no BFR-PRACH transmission in subframe i,power may be adjusted such that {circumflex over (P)}_(BFR-PRACH)(i)=0.

A wireless device may trigger, in subframe i, a BFR-PRACH transmissionon a serving cell, a PUSCH transmission with UCI on serving cell j, anda PUSCH without UCI in any of the remaining serving cells. If thisoccurs, and the total transmit power of the wireless device would exceed{circumflex over (P)}_(CMAX)(i), the wireless device may scale{circumflex over (P)}_(PUSCH,c)(i) for the serving cells without UCI insubframe i such that the condition

${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{{BFR}\text{-}{PRACH}}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right)$

may be satisfied, wherein {circumflex over (P)}_(PUSCH,j)(i) is a PUSCHtransmit power for the cell with UCI. If the above occurs, no powerscaling may be performed for {circumflex over (P)}_(BFR-PRACH)(i) and{circumflex over (P)}_(PUSCH,j)(i) unless

${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} = 0$

and the total transmit power of the wireless device still would exceed{circumflex over (P)}_(CMAX)(i). If there is no BFR request transmissionusing a BFR-PRACH in subframe i, power may be adjusted such that{circumflex over (P)}_(BFR-PRACH)(i)=0.

A wireless device may trigger, in subframe i, a BFR request transmissionusing a BFR PRACH on a serving cell, a simultaneous PUCCH and PUSCHtransmission with UCI on serving cell j, and PUSCH transmission withoutUCI in any of the remaining serving cells. If this occurs, and the totaltransmit power of the wireless device would exceed {circumflex over(P)}_(CMAX)(i), the wireless device may obtain {circumflex over(P)}_(PUSCH,c)(i) according to

P̂_(PUSCH, j)(i) = min (P̂_(PUSCH, j)(i), (P̂_(CMAX)(i) − P̂_(BFR-PRACH)(i) − P̂_(PUCCH)(i)))and${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq {\left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{{BFR}\text{-}{PRACH}}(i)} - {{\hat{P}}_{PUCCH}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right).}$

A wireless device, configured with a BFR-PRACH on a serving cell, whichis transmitted in parallel with an SRS transmission in different servingcells, may drop the SRS transmission if the total power for paralleltransmission of the BFR-PRACH transmission and the SRS transmissionwould exceed a configured or predefined value (e.g., P_(CMAX)).

The power adjustment of step 2310 may be performed if a base stationconfigures a wireless device with other uplink channels to transmit aBFR request (e.g., an SR/PUCCH). For example, a base station mayconfigure a wireless device with an SR/PUCCH for a BFR requesttransmission (e.g., BFR-PUCCH). The wireless device may determine uplinktransmission power as described above regarding step 2310 bysubstituting BFR-PUCCH for BFR-PRACH.

Transmissions may resume using the adjusted values in step 2314, e.g.,after adjusting the transmission power according to the priority such asdescribed above.

At step 2311, the wireless device may determine if a BFR-PRACHtransmission is prioritized over other types of PRACH transmissions. Forexample, a configuration parameter received from the base station mayindicate that a BFR-PRACH transmission is prioritized over other typesof PRACH transmissions. The BFR-PRACH transmission may be predefined orpreconfigured to be prioritized over other types of PRACH transmissions.If a BFR-PRACH transmission is determined to be prioritized over othertypes of PRACH transmissions, the method may continue at step 2312. If aBFR-PRACH transmission is determined to not be prioritized over othertypes of PRACH transmissions, the method may continue at step 2313.

At step 2312, the wireless device may adjust transmission power based ondetermining that a BFR-PRACH transmission is determined to beprioritized over other types of PRACH transmissions. If a wirelessdevice transmits a normal PRACH preamble on a serving cell in parallelwith a BFR request transmission on a BFR-PRACH on another serving cell,the wireless device may adjust the transmission power of the normalPRACH so that the total transmission power of the wireless device doesnot exceed a configured or predefined value (e.g., P_(CMAX)).

If a wireless device triggers a BFR request transmission on a BFR-PRACHin a serving cell in parallel with a normal PRACH transmission in adifferent serving cell, the wireless device may drop the normal PRACHtransmission if the total power for parallel transmission of theBFR-PRACH transmission and the normal PRACH transmission would exceed aconfigured or predefined value (e.g., P_(CMAX)).

The power adjustment of step 2312 may be performed if a base stationconfigures a wireless device with other uplink channels to transmit aBFR request (e.g., a SR/PUCCH). For example, a base station mayconfigure a wireless device with a SR/PUCCH for a BFR requesttransmission (e.g., BFR-PUCCH). The wireless device may determine uplinktransmission power as described above regarding step 2312 bysubstituting BFR-PUCCH for BFR-PRACH.

Transmissions may resume using the adjusted values in step 2314, e.g.,after adjusting the transmission power according to the priority such asdescribed above.

At step 2313, the wireless device may adjust transmission power based ondetermining that a BFR-PRACH transmission is determined to not beprioritized over other types of PRACH transmissions. If a wirelessdevice transmits a normal PRACH preamble on a serving cell in parallelwith a BFR request transmission on a BFR-PRACH on another serving cell,the wireless device may adjust the transmission power of the BFR-PRACHso that the total transmission power of the wireless device does notexceed a configured or predefined value (e.g., P_(CMAX)).

A wireless device may transmit a normal PRACH preamble in a RACHprocedure (e.g., initial access or handover).

If a wireless device triggers a BFR request transmission on a BFR-PRACHin a serving cell in parallel with a normal PRACH transmission in adifferent serving cell, the wireless device may drop the BFR-PRACHtransmission if the total power for parallel transmission of theBFR-PRACH transmission and the normal PRACH transmission would exceed aconfigured or predefined value (e.g., P_(CMAX)).

A wireless device configured with a BFR-PRACH transmission on a servingcell, which is transmitted in parallel with an SRS transmission indifferent serving cells, may drop the SRS transmission if the totalpower for parallel transmission of the BFR-PRACH transmission and theSRS transmission would exceed a configured or predefined value (e.g.,P_(CMAX)).

The power adjustment of step 2313 may be performed if a base stationconfigures a wireless device with other uplink channels to transmit aBFR request (e.g., a SR/PUCCH). For example, a base station mayconfigure a wireless device with a SR/PUCCH for a BFR requesttransmission (e.g., BFR-PUCCH). The wireless device may determine uplinktransmission power as described above regarding step 2313 bysubstituting BFR-PUCCH for BFR-PRACH.

Further power adjustments may be made for various other considerations,such as multiple TRPs. A wireless device may trigger a first BFR requeston a first BFR-PRACH on a first TRP (e.g., using RSs), which may betransmitted in parallel with a second BFR request transmission on asecond BFR-PRACH on a second TRP (e.g., using RSs). A wireless devicemay adjust the transmission power of the second BFR-PRACH so that thetotal transmission power of the wireless device does not exceed aconfigured or predefined value (e.g., P_(CMAX)).

The second BFR-PRACH may be associated with a TRP (e.g., using RSs) witha lower beam pair link quality. The second BFR-PRACH may be associatedwith a TRP (e.g., using RSs) which may be a particular TRP (e.g., usingRSs) indicated by a base station.

A wireless device may trigger a first BFR request on a first BFR-PRACHon a first TRP (e.g., using RSs), which may be transmitted in parallelwith a second BFR request transmission on a second BFR-PRACH on a secondTRP (e.g., using RSs). A wireless device may drop the second BFR-PRACHtransmission if the total power for parallel transmission of bothBFR-PRACH transmissions would exceed a configured or predefined value(e.g., P_(CMAX)).

A wireless device may trigger a BFR-PRACH transmission in a TRP (e.g.,using RSs), which may be transmitted in parallel with a PUCCHtransmission or a PUSCH transmission in a different TRP (e.g., usingRSs). The wireless device may allocate the transmit power for theBFR-PRACH and the other channels by using one or more of the methodsherein, substituting a “TRP” for a “cell.”

Power adjustments may also be made to compensate for overlappingtransmission in a single cell. A wireless device may be configured withone serving cell. If a wireless device triggers a BFR-PRACH in parallelwith an uplink channel transmission, the wireless device may determinetransmit power for the BFR-PRACH and the other channel by using one ormore of the methods described herein.

A wireless device may trigger a BFR request on a BFR-PRACH in parallelwith a PUSCH transmission or a PUCCH transmission in a serving cell. Thewireless device may adjust the transmission power of the PUCCH or PUSCHso that the total transmission power of the wireless device does notexceed a configured or predefined value (e.g., P_(CMAX)).

A wireless device may trigger a BFR request on a BFR-PRACH in parallelwith a PUSCH with UCI transmission or a PUCCH transmission in a servingcell. The wireless device may adjust the transmission power of the PUSCHwith UCI so that the total transmission power of the wireless devicedoes not exceed a configured or predefined value (e.g., P_(CMAX)).

A wireless device may trigger a BFR request on a BFR-PRACH in parallelwith a PUSCH transmission or a PUCCH transmission in a serving cell. Thewireless device may adjust the transmission power of the BFR-PRACH and aPUSCH without UCI so that the total transmission power of the wirelessdevice does not exceed a configured or predefined value (e.g.,P_(CMAX)).

A wireless device may trigger a BFR request on a BFR-PRACH in parallelwith a normal PRACH transmission in a serving cell. The wireless devicemay adjust the transmission power of the BFR-PRACH so that the totaltransmission power of the wireless device does not exceed a configuredor predefined value (e.g., P_(CMAX)).

A wireless device may trigger a BFR request on a BFR-PRACH in parallelwith a normal PRACH transmission in a serving cell. The wireless devicemay adjust the transmission power of the normal PRACH so that the totaltransmission power of the wireless device does not exceed a configuredor predefined value (e.g., P_(CMAX)).

A base station may configure a wireless device with other uplinkchannels to transmit a BFR request (e.g., an SR/PUCCH). The powerallocation procedure in this example may be performed for the channel.For example, a base station may configure a wireless device with anSR/PUCCH for a BFR request transmission (e.g., BFR-PUCCH). The wirelessdevice may determine uplink transmission power as described aboveregarding step 2313 by substituting BFR-PUCCH for BFR-PRACH.

At step 2314, the wireless device may resume transmission using adjustedtransmission power values. For example, transmission power values for aBFR-PRACH, PUCCH, PUSCH, and/or normal PRACH may be adjusted asdescribed in steps 2305 to 2313. Transmission may continue on respectivechannels according to the adjusted values.

If the wireless device determines that the adjusted transmission powervalues are no longer needed, the wireless device may increase powervalues or return to default values. For example, the wireless device maydetermine that a beam failure recovery process has concluded. Based ondetermining that the beam failure recovery process has concluded, thewireless device may return transmission power values to default values(e.g., transmission power values as determined in step 2304).

Any base station may perform any combination of one or more of the abovesteps of FIG. 23. A wireless device, a core network device, or any otherdevice, may perform any combination of a step, or a complementary step,of one or more of the above steps. Some or all of these steps may beperformed, and the order of these steps may be adjusted. For example, awireless device may perform one or more steps of 2305, 2306, 2313 or2314. If the wireless device determines that a BFR-PRACH transmission isprioritized over a PUCCH transmission, the wireless device may performadjusting transmission power according to step 2306. If the wirelessdevice determines that a BFR-PRACH transmission is prioritized below aPUCCH transmission, the wireless device may perform adjustingtransmission power according to step 2313. After the transmission poweradjustment, the wireless device may transmit the BFR-PRACH and/or thePUCCH according to the adjusted transmission power value. For example, awireless device may perform one or more steps of 2307, 2308, 2313 or2314. For example, a wireless device may perform one or more steps of2309, 2310, 2313 or 2314. For example, a wireless device may perform oneor more steps of 2311, 2312, 2313 or 2314. For example, the wirelessdevice may perform steps of 2305, 2307, 2309 and/or 2311 in parallel, orin any order. For example, one or more of steps 2305 to 2311 may not beperformed for overlapping transmission in a single cell. As otherexamples, step 2305 and/or step 2304 may be performed before step 2303.Results of one or more of steps 2305 to 2313 may be weighted differentlyfrom results of one or more other of these steps for an overall decisionrelating to an adjustment of transmission power and/or a transmissionusing an adjusted transmission power.

FIG. 24 shows an example of processes for a base station for beamfailure recovery requests. These processes may be complementary of theprocesses for a wireless device for beam failure recovery requestsdepicted in FIG. 23. A base station may, at step 2401, transmit amessage comprising one or more configuration parameters. For example,the base station may transmit configuration parameters such as thosereceived by a wireless device in FIG. 23. The configuration parametersmay comprise priority information for a BFR PRACH transmission. Theconfiguration parameters may indicate the BFR-PRACH priority used in thedeterminations above (e.g., steps 2305, 2307, 2309, or 2311). Forexample, the BFR-PRACH priority may be predefined or preconfigured. Thetransmitted parameters may comprise first parameters for a BFR procedureof a first cell (which may indicate RSs and first RACH resources), aswell as second parameters for random access procedures for a second cellassociated with second RACH resources. After transmitting theconfiguration parameters, the base station may begin monitoring RACHresources at step 2402.

At step 2402, the base station may monitor RACH resources associatedwith a cell. The base station may monitor the first RACH resources, aswell as the second RACH resources.

At step 2403, the base station may detect a first preamble (e.g., a RAP)transmitted from a wireless device via the first RACH resources. Thebase station may detect, at step 2404, a beam failure related to thefirst RACH resources. The base station may detect the beam failure inthe manner described above for beam failure detection (e.g., step 2303of FIG. 23).

At step 2405, the base station may transmit, based on the firstpreamble, a control signal to the wireless device. The base station maytransmit the control signal based on the detected beam failure. Thecontrol signal may comprise downlink control information. The controlsignal may indicate priority information for transmissions from thewireless device. For example, the control signal may indicate a priorityfor BFR-PRACH transmissions. The control signal may indicate theBFR-PRACH priority used in the determinations above (e.g., steps 2305,2307, 2309, and/or 2311). The control signal may indicate a secondpreamble and/or a second RACH resource for a second RACH procedure.

At step 2406, the base station may detect a second preamble (e.g., aRAP) transmitted from the wireless device via the second RACH resources.The base station may transmit, at step 2407, a media access controlprotocol data unit (MPDU) to the wireless device.

Any base station may perform any combination of one or more of the abovesteps of FIG. 24. A wireless device, a core network device, or any otherdevice, may perform any combination of a step, or a complementary step,of one or more of the above steps. Some or all of these steps may beperformed, and the order of these steps may be adjusted. For example,one or more of steps 2403 to 2405 may not be performed. As anotherexample, step 2405 to 2407 may be performed before, or concurrentlywith, step 2402. Results of one or more of steps 2401 to 2407 may beweighted differently from results of one or more other of these stepsfor an overall decision relating to an adjustment of transmission powerand/or a transmission using an adjusted transmission power.

A base station may perform any combination of one or more of the abovesteps. A wireless device, or any other device, may perform anycombination of a step, or a complementary step, of one or more of theabove steps. Any base station described herein may be a current basestation, a serving base station, a source base station, a target basestation, or any other base station. A system may comprise a wirelessdevice and a base station.

FIG. 25 shows general hardware elements that may be used to implementany of the various computing devices discussed herein, including, e.g.,the base station 401, the first base station 1502, the second basestation 1503, the base station 2101, the wireless device 406, thewireless device 1501, the wireless device 2102, the wireless device2202, or any other base station, wireless device, or computing device.The computing device 2500 may include one or more processors 2501, whichmay execute instructions stored in the random access memory (RAM) 2503,the removable media 2504 (such as a Universal Serial Bus (USB) drive,compact disk (CD) or digital versatile disk (DVD), floppy disk drive),or any other desired storage medium. Instructions may also be stored inan attached (or internal) hard drive 2505. The computing device 2500 mayalso include a security processor (not shown), which may executeinstructions of one or more computer programs to monitor the processesexecuting on the processor 2501 and any process that requests access toany hardware and/or software components of the computing device 2800(e.g., ROM 2502, RAM 2503, the removable media 2504, the hard drive2505, the device controller 2507, a network interface 2509, a GPS 2511,a Bluetooth interface 2512, a WiFi interface 2513, etc.). The computingdevice 2500 may include one or more output devices, such as the display2506 (e.g., a screen, a display device, a monitor, a television, etc.),and may include one or more output device controllers 2507, such as avideo processor. There may also be one or more user input devices 2508,such as a remote control, keyboard, mouse, touch screen, microphone,etc. The computing device 2500 may also include one or more networkinterfaces, such as a network interface 2509, which may be a wiredinterface, a wireless interface, or a combination of the two. Thenetwork interface 2509 may provide an interface for the computing device2500 to communicate with a network 2510 (e.g., a RAN, or any othernetwork). The network interface 2509 may include a modem (e.g., a cablemodem), and the external network 2510 may include communication links,an external network, an in-home network, a provider's wireless, coaxial,fiber, or hybrid fiber/coaxial distribution system (e.g., a DOCSISnetwork), or any other desired network. Additionally, the computingdevice 2500 may include a location-detecting device, such as a globalpositioning system (GPS) microprocessor 2511, which may be configured toreceive and process global positioning signals and determine, withpossible assistance from an external server and antenna, a geographicposition of the computing device 2500.

The example in FIG. 25 is a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 2500 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 2501, ROM storage 2502, display 2506, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 25.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

One or more features of the disclosure may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above mentioned technologiesmay be used in combination to provide the result of a functional module.

Systems, apparatuses, and methods may perform operations ofmulti-carrier communications described herein. Additionally oralternatively, a non-transitory tangible computer readable media maycomprise instructions executable by one or more processors configured tocause operations of multi-carrier communications described herein. Anarticle of manufacture may comprise a non-transitory tangible computerreadable machine-accessible medium having instructions encoded thereonfor enabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a UE, a base station, and the like) toenable operation of multi-carrier communications described herein. Thedevice, or one or more devices such as in a system, may include one ormore processors, memory, interfaces, and/or the like. Other examples maycomprise communication networks comprising devices such as basestations, wireless devices or user equipment (UE), servers, switches,antennas, and/or the like. Any device (e.g., a wireless device, a basestation, or any other device) or combination of devices may be used toperform any combination of one or more of steps described herein,including, e.g., any complementary step or steps of one or more of theabove steps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the disclosure. Accordingly, theforegoing description is by way of example only, and is not limiting.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, one or more radio resource control messages comprising: firstconfiguration parameters of at least one cell; and second configurationparameters of a random access procedure for a beam failure recovery;after at least one beam failure on a first cell of the at least onecell, initiating the random access procedure for the beam failurerecovery; determining, based on the second configuration parameters, afirst transmission power of a first preamble. determining that a firstconfigured transmission, of the first preamble via the first cell,overlaps in time with a second configured transmission of a secondpreamble; adjusting a second transmission power of the second preambleso that a total power, comprising the first transmission power and asecond transmission power of the second configured transmission, doesnot exceed a total allowable power value; and transmitting, using theadjusted second transmission power, the second preamble.
 2. The methodof claim 1, further comprising detecting, based on determining that ameasured beam link quality value is below a threshold, the at least onebeam failure.
 3. The method of claim 2, wherein the measured beam linkquality value is based on at least one of: a reference signal receivedpower; or a reference signal received quality.
 4. The method of claim 1,further comprising transmitting, using the first transmission power, thefirst preamble.
 5. The method of claim 1, further comprising: selecting,based on the initiating the random access procedure for the beam failurerecovery, the first preamble from a plurality of preambles.
 6. Themethod of claim 1, further comprising initiating a second random accessprocedure based on at least one of: an initial access procedure; ahandover command; or a physical downlink control channel order.
 7. Themethod of claim 1, wherein: the at least one cell is grouped intomultiple cell groups; the first cell is a primary cell of a first cellgroup of the multiple cell groups; and the transmitting the secondpreamble is via a second cell that is a secondary cell of a second cellgroup of the multiple cell groups.
 8. A method comprising: receiving, bya wireless device, one or more radio resource control messagescomprising: first configuration parameters of at least one cell; andsecond configuration parameters of a random access procedure for a beamfailure recovery; after at least one beam failure on a first cell of theat least one cell, initiating the random access procedure for the beamfailure recovery; determining, based on the second configurationparameters, a first transmission power of a preamble; determining that afirst configured transmission, of the preamble via the first cell,overlaps in time with a second configured transmission of a secondsignal; and based on a determination that a total power, comprising thefirst transmission power and a second transmission power of the secondconfigured transmission, exceeds a total allowable power value: droppingthe second signal.
 9. The method of claim 8, further comprisingdetecting, based on determining that a measured beam link quality valueis below a threshold, the at least one beam failure.
 10. The method ofclaim 9, wherein the measured beam link quality value is based on atleast one of: a reference signal received power; or a reference signalreceived quality.
 11. The method of claim 8, further comprisingtransmitting, using the first transmission power, the preamble.
 12. Themethod of claim 8, further comprising: selecting, based on theinitiating the random access procedure for the beam failure recovery,the preamble from a plurality of preambles.
 13. The method of claim 8,further comprising initiating a second random access procedure based onat least one of: an initial access procedure; a handover command; or aphysical downlink control channel order.
 14. The method of claim 8,wherein: the at least one cell is grouped into multiple cell groups; thefirst cell is a primary cell of a first cell group of the multiple cellgroups; and the second configured transmission is configured to betransmitted via a second cell that is a secondary cell of a second cellgroup of the multiple cell groups.
 15. A method comprising: receiving,by a wireless device, one or more radio resource control messagescomprising: first configuration parameters of at least one cell; andsecond configuration parameters of a beam failure recovery; afterdetecting at least one beam failure on a first cell of the at least onecell, initiating a scheduling request procedure for the beam failurerecovery; determining a first transmission power of a configuredtransmission via the first cell of a first signal associated with thescheduling request procedure. determining that the configuredtransmission of the first signal overlaps in time with a configuredtransmission of a second signal; and based on a determination that atotal power, comprising the first transmission power and a secondtransmission power of the configured transmission of the second signal,exceeds a total allowable power value: adjusting the second transmissionpower so that the total power does not exceed the total allowable powervalue; or dropping the second signal.
 16. The method of claim 15,wherein the second signal is for an uplink transmission via at least oneof: a physical uplink control channel; or a physical uplink sharedchannel.
 17. The method of claim 15, wherein the second signal is asounding reference signal.
 18. The method of claim 15, wherein: thefirst signal is for an uplink transmission via a first physical randomaccess channel; and the second signal is for an uplink transmission viaa second physical random access channel.
 19. The method of claim 15,further comprising transmitting, using the first transmission power, thefirst signal.
 20. The method of claim 19, further comprisingtransmitting, using the adjusted second transmission power, the secondsignal.